Apple MacBook Pro with M1 Review

Post by cma » Tue, Nov 17, 2020, 6:30 PM UTC

pembrook wrote: post #37

zepto wrote: post #26

“Apple’s insistence that reaching up to touch a laptop screen is too burdensome is just getting silly, especially when that is not a problem on the iPad and across the universe of Windows laptops, and most especially when these laptops can run iPhone and iPad apps natively.“ In a way Nilay is right - ultimately it makes no sense not to allow touch interaction. However Apple is also right in a different way. If apps a…

Not only is most desktop software not well suited to touch interactions, touchscreens on laptops are also an ergonomic nightmare. Try reaching your hand up to touch your monitor and hold it there for a minute. Now try pretending you’ll do this for an 8 hour workday. It’s a useless feature in search of a use-case.

Post by qz2 » Tue, Nov 17, 2020, 6:43 PM UTC

Eric_WVGG wrote: post #46

qz2 wrote: post #8

Earlier quoted context omitted.

Because Microsoft, much like most of the ecosystems around ARM, didn't build their own CPU. They got an off the shelf mobile chipset, customised it slightly, rebranded it and then chucked the whole shit heap of windows on top.

I have also heard that Microsoft put lower priority on the x86 emulation layer, because they felt like if it was really good, developers would have no incentive to make native compiles. While this sounds instinctively ridiculous to me, as of late I’ve become very cognizant of general laziness in our industry, so who knows…

Post by diebeforei485 » Tue, Nov 17, 2020, 6:51 PM UTC

slg wrote: post #49

pembrook wrote: post #37

Earlier quoted context omitted.

Not only is most desktop software not well suited to touch interactions, touchscreens on laptops are also an ergonomic nightmare. Try reaching your hand up to touch your monitor and hold it there for a minute. Now try pretending you’ll do this for an 8 hour workday. It’s a useless feature in search of a use-case.

>It’s a useless feature in search of a use-case. This was true until just now. The use case is right at the end of OP's quote. These laptops now run iOS apps that are designed with touch as their primary or only interface. It is weird to include the functionality to run these apps but not the functionality to interact with them properly.

Post by joking » Tue, Nov 17, 2020, 6:56 PM UTC

jamil7 wrote: post #9

danpalmer wrote: post #4

It's worth noting that while there are still quite a few caveats to the M1 MacBook Pro when looking at "pro workflows", this is only intended to replace the "low end" MacBook Pro which was already quite restricted. Given all the missing parts could require a fair bit more development (eGPU support is not something iPhones have needed so far after all), I expect we'll see these on the next generation of CPUs, along wi…

I don't think we'll see a Mac Pro for a long time, this will be the most difficult (and interesting) one to see move over to ARM.

Post by Skunkleton » Tue, Nov 17, 2020, 7:03 PM UTC

tonymet wrote: post #55

oatmeal_croc wrote: post #7

Is any web developer planning to get the new Apple Silicon Macs? How's docker support (for ARM and x86 images)? Do the major IDEs work on Rosetta? What's support looking like for languages like GO, Rust now/in the near future?

Docker images are meant to be built once and run everywhere–tested on your dev server, test environment and production. If you buy an ARM mac, it would be ideal to run ARM instances in the datacenter, but those are uncommon and expensive. I discourage people from building ARM images and then rebuilding intel images later in the software lifecycle.