I've been supportive of this move since I first heard about it as a rumor over a year ago. Intel is a sinking ship in many ways. They are far too unreliable and they were causing Apple all sorts of problems.
Even since the unveiling of Big Sur, for some reason I've had a change of heart. Something about that OS just doesn't appeal to me. Being locked in to Apple's ecosystem without the chance to run Windows and Linux without emulation is concerning.
Possible lack of compelling software apps. No old games like GTA III. I'm starting to think buying a final gen Intel Mac is the best way to go, considering it will be supported by Apple for at least 5 years and fully compatible with Windows and Linux for as long as you own it.
Anyone else feel this way?
I can empathize with your feelings here.
On paper, Apple transitioning the Mac to their own ARM SoCs makes too much sense. Assuming developers play along and transition their apps over, it will be a fantastic move for the future of the platform, especially given their desires to provide parity between macOS and their other platforms. If you are an avid macOS user, then the potential is pretty great!
However, whatever PC gaming was able to be done on a Mac (either natively in macOS or via Boot Camp) takes a hit with this move. And the freedom to run other operating systems on your Mac (either via dual-booting or via VMware Fusion or Parallels Desktop) takes a hit given that there are WAY more x86 operating systems that you can run out there than there are ARM ones.
Seeing as these are two very important things for me as a computer user (let alone a Mac user), I'm not going to wait for ARM. I'm going to get an Intel Mac in the not-too distant future and that'll be what I roll with. Macs will Apple Silicon will be waiting for me. Suffice it to say, if your main second thoughts revolve around these functions, then I definitely empathize. The Intel Mac era was a great era that produced the best of the Macintosh, by far. We know little about what's coming.
I'd say that, if you can afford it, get a really great Intel Mac today, and keep an open mind for the future. Certainly, as far as macOS and compatible apps are concerned, we've got some pretty great performance coming up in the new era.
Linux can be run with virtualization. There are many ports with arm64 already. so I suspect Linux is a non issue.
Yes and no. Currently, the server variant for Ubuntu has an ARM port. The standard non-server version does not. ARM is still up and coming as a desktop architecture thanks to the Raspberry Pi (remember, it's much more common as a mobile architecture). Your mileage will vary, but for now, assume that selection is still somewhat limited. This may be why Apple's current stance on direct booting a non-macOS OS is what it currently is.
There is a remote possibility of running Windows with virtualization as well (if Microsoft allows it). But the Windows situation won’t be the same since most Windows software is not compiled for arm64.
32-bit x86 Windows software runs fine on Windows 10 for ARM64. The emulation layer is slow, but that's because, up until now, the SoCs used on ARM64 PCs have been slow. You're only unable to run 64-bit x86 software. However, Windows software that is exclusively 64-bit x86 is extremely rare given that Microsoft hasn't put the gun to developers' heads about it the way Apple did with Catalina.
I could be wrong but since the new Apple silicon Macs will likely be much more powerful (cpu and gpu) and energy efficient -this might attract more developers to the Mac platform.
Unlike Kelis' Milkshake, having the better (more efficient, faster, etc.) platform doesn't necessarily bring all the boys to the yard. This is why tvOS hasn't taken off as a console gaming platform despite both supported Apple TV models having adequate graphics performance for console-level gaming. Apple's SoC's are powerful and efficient, but that doesn't necessarily equate support from developers that have spent most of their time developing for more traditional computing/graphics architectures (despite their relative inefficiency).
Personally I’m absolutely loving Big Sur and can’t wait for ARM Macs to start showing up.
I’ll be a Day One purchaser of either the 14” or 16” MBP - whichever comes first.
I bought the first Intel 20" iMac back in 2006. It was fun being an early adopter to that switch, despite not having many of my pro apps function for a bit or many of my games work well (or at all). And I'm grateful that I got the 20" iMac rather than the first 15" MacBook Pro.
I think this time, I'll be content to buy a final gen Intel Mac and watch (and support) others buying early, so that when I make the jump a few years down the line, I'll know what I'm getting into and be more ready to get into it.
I’m super excited, but I will admit I do have one reservation now that I didn’t consider before.
I just bought a 2018 15” MacBook Pro a little over a year ago and it was the most I’ve ever spent on a computer or device. It still runs like new and I was hoping to use it about 5 years at least, which is how long I used my old MacBook Pro. However, now I’m concerned about how long intel support will last. I really don’t feel like shelling out a lot of money again anytime soon and the fact that my resale value for it will tank makes it worse.
I would imagine that a 2018 15" MacBook Pro would remain supported for macOS releases at least through 2026, if not a hair past that point (and don't forget that you still get security patches on your last supported OS for two years after that point). These days (as opposed to the days at the start of the Intel switch), Apple drops support for machines it either can't procure updated versions of every driver for or that don't support a feature they deem critical to that release of macOS (i.e. Mojave dropping support for Macs with GPUs/IGPs that don't support Metal). Apple will inevitably have incentive to stop updating the Intel codebase, just as they did with the PowerPC codebase with Snow Leopard, but those days are a long way off (and Apple has many many more active Intel users now than they did PowerPC users at this point in that transition).
Intel support should be anywhere from 3 to 7 years after the Apple Silicon transition is complete. I would say half of that as system updates, the other half as security updates. But just because the unit is not receiving system updates does not mean it will not work with the OS it has! So use what you got for a handful more of years, then get in on a third-gen Apple Silicon machine!
7 years is a little conservative, given that 2012 Macs are only now getting left out of the next major OS release some 8 years later. Mind you the predecessors for most of those Macs had 7 years (though some of their predecessors lost support on the same day). Our mileage will totally vary in terms of when a Mac loses support. It's safe to say that systems based on 9th and 10th Gen Intel will be supported for a good while. 8th Gen too. The only exception that might be worth worrying about is the current iMacs. If Apple deems a feature important to the platform that requires a Mac with a Secure Enclave in the same fashion that they deemed Metal support on Macs to be critical, we might see the dropping of support of every Mac that doesn't have one (which would mean that 9th Gen based Intel 27" iMacs would lose support sooner than some 8th Gen based Intel Macs in that hypothetical scenario).
Actually there is a reasonable chance the late Intel Macs will hold some value as the last ones capable of x86 Windows.
They may not hold and more monetary value for being Intel Macs. But certainly, you will be able to run newer versions of Windows 10 after your Apple has stopped supporting your Mac for new macOS releases. Case in point: 2012 Macs will STILL be able to run a current version of Windows 10 after Big Sur leaves them out.
Just be mindful that developers will dump Intel/Universal binary just as quickly as they can. The current/next version of software on your Intel Mac might be the last. As soon as Apple rolls out an ARM based Mac, there will be developers who will skip universal binary as they port to the new code. While Rosetta offers compatibility for x86 to ARM, it won’t run in reverse. Universal binary is a good tool to have while moving into the transition, but Rosetta working x86 to ARM to x86, would have been better. It would have allowed Intel Macs running Big Sur to install iOS apps on the Mac. It also would have allowed Intel customers longevity with developers who will be crappy about the transition.
I went through the 68k to PPC transition and the PPC to Intel transition. Both were desperately needed. Maybe this transition is desperately needed too. Perhaps Apple needs a pro line of computers running AMD chipsets for x86 compatibly and perhaps their pro portables should have active cooling along with Ethernet port. A card slot, and at least one HDMI port, a professional grade machine. I don’t know the answers but Apple has a game plan and it has worked before. But I would find a replacement for the app you’re holding onto. A subscription model is the reason I abandoned adobe for better/cheaper software from their competitors. The moment Apples iWork suite can export reliable word docs or excel spreadsheets, I’m done with office 365, but I digress.
This is not the PowerPC to Intel transition. Apple has many more Intel Mac users heading into this transition than they ever did PowerPC users headed into the Intel transition. Developers will be foolish to drop support for Intel prematurely. I do agree that it will inevitably happen. But it won't happen that fast with most key developers. Where you will likely see this will be with Mac games that were originally ported over from Windows (but never fully received the Metal make-over). You'll also likely see it with software that doesn't get regular rolling updates. I would also guess that software that made the move to 64-bit begrudgingly so that it could still run in Catalina is also in danger. But then again, for much of those titles, you simply might not see an ARM release. Porting x86 Windows code to x86 macOS isn't as big of a challenge as porting x86 Windows code to macOS on another architecture. This is why, following the switch to Intel, we saw a surge in new Mac software (games especially included). It's much more likely that you're going to see some Mac developers leave the platform due to having mainly been there for x86 parity.
the main problem with a one way translator and a universal binary is that you have developers who will bail & fail. They will bail on the platform and they will fail to offer support. The good developers will port with universal binary. There are many of those. And some developers will release their next new version, replete with new features in universal binary. That version will have many point updates as they squash bugs and optimize their new code and get development processes lined up. That set of developers will not release another version under universal binary. They gave you one last hurrah as they streamlined their roadmap.
The last type of developer will release bug fixes for Intel code starting now. If the first apple silicone Mac rolls out in September 2020, that’s when Intel code is gone for them. They will release a final round of patches/bug fixes in the pipeline and they will wait a few months to release the new version of their software which they started developing as soon as the developer support became available from Apple (WWDC). They will stop making new code even though Intel Macs are still rolling off the assembly line. Any hardware that might need a driver or software support- same problem.
Developer support starts dying long before MacOS updates. I’m a little surprised some smart apple Engineer didn’t pipe up and suggest a two-way Rosetta translation layer.
Again, I think that you're going to continue to see Universal Binaries for as long as Apple is releasing Intel-supported releases of macOS. As soon as Apple drops support for Intel in future macOS releases, that'll be when Universal Binaries follow suit.
YES!!! I'll gladly trade in the ability to play RDR2, Fallen Order, Witcher 3 in bootcamp on my MBP 16 for Candy Crush and some Animal Crossing!! /s
Seriously though, Mac gaming selection was pathetic during the PPC era and we're definitely going back there with AAA titles never being ported or about 2-3 years later.
I'll just continue to use my MBP 16 for now and later get a 2nd/3rd gen ARM and might just have to carry a Razer 13 for gaming on the road....
Mac gaming had a surge in 2010-2012 with Steam on the Mac. My guess is that Valve is not going to be keen on supporting ARM in any way (they only have two of their games with 64-bit Intel at this point!). Considering how few Mac games from Aspyr and Feral Interactive survived Catalina's Culling(tm), this could be indicative of the end of triple-A titles from PC also making their way to Mac.
I do have a feeling that Blizzard will update their non-Overwatch games for the new architecture. I do, however, think that the Apple Silicon switch means that it will be less likely that we will see an Overwatch Mac release, however.
With virtualization, Microsoft wouldn't really have to allow it; VMWare or Parallels (the latter of which I believe is already working on it) just needs to have an x86 emulation shell sitting on top of the OS. It will be potentially a lot slower, like the old days when people ran Windows VM's on G4's.
Emulation and Virtualization are not the same thing. An x86 operating system running in VM on an ARM processor requires emulating that architecture. And, like you said, there will be a speed hit. The person you were replying to was talking about virtualizing the ARM64 version of Windows 10 which has licensing constraints (imposed by Microsoft, for the time being) that the x86 and x86-64 versions of Windows 10 do not. Virtualizing the ARM64 version of Windows 10, while not being helpful for those wanting to run a 64-bit x86 Windows app, would still be faster than emulating the x86 architecture for an entire system. VMware has all but stated that a would-be version of Fusion for Mac for ARM wouldn't run x86 VMs. It's very likely that Parallels will have a similar policy and/or such a policy might even be dictated by Apple.
I think Kuo has missed the mark. His two predictions make no business sense in light of information we have. Knowing my luck the 16" MBP will be first with ARM.
If Apple starts churning out faster, cooler, thinner, sexier machines with better battery life, PC manufacturers will want to try ARM. Hard to say who will make the CPUs for them but Microsoft will want to cater and probably get Windows 10 or 11 running with 64-bit support on ARM. I imagine they'll license it for virtualisation on Mac too to make sure they are monetising it as best they can.
The 13" MacBook Pro is looking like it will be the first with ARM, not the 16". This isn't a matter of making "business sense" or not. Apple has the capability to put out a machine with their SoCs that handily outperforms any and all Intel-based 13" MacBook Pros TODAY. The same isn't necessarily a given for all Intel-based 16" MacBook Pros TODAY. Apple might be able to best the 6-core i7 models TODAY, but the 8-core i9 models aren't necessarily a given. And Apple is not about to release an Apple Silicon 16" MacBook Pro replacement that doesn't outperform every 16" and 15" MacBook Pro that has ever existed. THAT would make no business sense.
As for Windows 10 on ARM64, I agree that Apple's hardware is a good reason for Microsoft to consider partnering with them to either get an Apple Silicon Mac dual-booting solution in order (a la Boot Camp for Intel Macs) or to at least get Windows 10 on ARM64 virtualized on Apple Silicon Macs. Macs benefit from supporting Windows and Windows 10 on ARM64 needs competent hardware to run on to demonstrate to Microsoft, consumers, and Windows application developers that it's not a lost cause.