71–80 of 116 posts
This device, and the non-Touch Bar "MacBook Escape" before it, succeed or fail based on what you think "Pro" means. John Gruber thinks when Apple says "Pro" they mean "deluxe" or "nicer". (See https://daringfireball.net/2015/11/the_ipad_pro for example.) You can argue that this could have been avoided by calling this particular device the MacBook. But that might have made people think it was the default choice, where…
There's nothing of any value in this diatribe disguised as a review.
Earlier quoted context omitted.
Apple shows no signs towards being interested in selling a touch screen laptop. They steer people to their iPads for that and have indicated otherwise for their laptops. Rightly or wrongly.
Jobs famously said quite strongly that they'd never do one. There is a video around of him justifying it due to the user's hands getting too tired https://www.youtube.com/watch?reload=9&v=S9ZJHy8QOso . After 12 years on Macs I picked up a touchscreen PC and would simply never go back to a non-touch machine, it is not essential, but it is incredibly convenient. Why shouldn't it be possible to touch rather than tap whe…
I will add this though. You can side car a tablet to your Big Sur Mac. Pretty sure it stays touchable through to the Mac client.
The limitation on just one external monitor at a time beggars belief in a Pro device. App crashes were not reported elsewhere. Aside from some subjective commentary, there's a genuinely different side shown in the review.
This review is hilariously bad and biased ("no touchscreen or 5G!"), but the app compatibility is an expected chicken-or-egg issue with early adopters. The point I would make is you have to weigh the app experience in Nov 2020 against your expected experience for the rest of the life of the machine. I know people who've kept Macs running for nearly a decade (e.g. 2011 Macbook Air) and I'd strongly suspect 5 years fro…
> If your main concern is running Zoom and OneNote for the next 6 months, maybe sit out M1 for now.
There is very little information out there about how M1 fits into developer workflow. It is not just Zoom and OneNote but app compatibility is very important for developers and I think most developers(except iOS devs) would perhaps want to sit out the release. There is no docker. VirtualBox will probably never work on Apple M1, so an escape to Linux VM is not available if you need. Parallels and Vmware Fusion may work someday but you will end up paying for those and someone should do performance/battery comparison if I am going to run a VM all day. Things like Emacs don't work yet and only information available about this is from obscure twitter threads.
This review is hilariously bad and biased ("no touchscreen or 5G!"), but the app compatibility is an expected chicken-or-egg issue with early adopters. The point I would make is you have to weigh the app experience in Nov 2020 against your expected experience for the rest of the life of the machine. I know people who've kept Macs running for nearly a decade (e.g. 2011 Macbook Air) and I'd strongly suspect 5 years fro…
I have a tangential question. Would there be any technical reason why Apple only released a 13" version of the Macbook pro with the new M1 chip and not any of the larger versions of the Macbook pro or would this likely be a 'refresh schedule" consideration?
Everything Apple does is automatically a huge plus for some people. may be, just may be, it's not for everyone
Does anyone know if the Rosetta issue described in the review would affect the performance of a Parallels instance running MS Office products? Maybe this question would be better phrased, does Parallels fall into the category of software that runs poorly on the new M1 chipset?