9 ms·
Apple’s Mac Chip Switch Is Double Trouble for Intel
- MintelIE 6y agoApple is "preparing to announce" the switch, but haven't we heard these rumors for, well, years now? How much more reliable are these rumors now compared to a couple years ago? I'm a little surprised to see Bloomberg basically cribbing MacRumors. EDIT: Instantly downvoted? LOL
- nicoburns 6y agoI always take these rumours with a pinch of salt. But I don't think that there having been rumours for years discredits them. There were apple tablet rumours for years too, which turned out to be because they were working on a tablet for about 10 years before they released it (they ended up releasing the iPhone first as part of the same project, and I believe that was 7 years in).
- valuearb 6y agoWhen I worked at Apple I ported FileMaker to a Macintosh Tablet computer almost 20 years before the iPad.
- bsorbo 6y agoSome analysts (including Gurman) have pretty consistently called out 2020 as “the” year for a couple years now: https://www.bloomberg.com/news/articles/2018-04-02/apple-is-said-to-plan-move-from-intel-to-own-mac-chips-from-2020 https://www.bloomberg.com/news/articles/2018-04-02/apple-is-...
- Bud 6y agoThe rumors were valid a couple years ago, too; any change like this would definitely take years of planning.
- evv 6y agoYou don’t need to rely on the rumors. Anybody who has seen the trend of Apple’s hardware can see that they are moving in this direction. The iPads have touted “desktop class” CPUs for years.. Macs already have in-house supervisor chips, (the T2 in the MacBook). Apple is a smart behemoth, an expert at vertical integration, who has a lot to benefit by cutting out Intel. They will certainly attempt it. It's only a question of how and when.
- neximo64 6y ago'Rumors' like this don't have exact dates like June 22nd.
- saagarjha 6y agoMacRumors is the one doing the cribbing this time around, as there are extremely strong supply chain rumors for a new ARM chip that would support a Mac lineup.
- albntomat0 6y ago(both of these are genuine questions, not rhetorical ones) 1. If x64 wasn't already dominant and had the same market share as ARM, would you choose x64? Why? 2. With x64's current dominance, would you buy a ARM system as your primary one, knowing that you'll have significant difficulties developing for the majority of current market share?
- hidiegomariani 6y agonoob here my thought is 1. arm is more power efficient than x64? 2. emulation + shift to remote development environments?
- albntomat0 6y agoIs the emulation environment really there? Maybe the nodejs (and everything not low level) can seamlessly develop on arm and ship on x64?
- remexre 6y agoI spent a week recently working from a Pinebook Pro after spilling water on my primary laptop; my workflow was already fairly SSH-centric, but I had fairly few problems with software compatibility that weren't fixed by binfmt_misc + qemu. (That week was spent mostly developing in OCaml and Lisp; I suspect if I were doing C++ or Haskell, I would've had a harder time.)
- tylerhou 6y agoOne theory behind ARM's power efficiency is that you don't have to waste power and area converting x86 into uops. But this is a constant overhead. It matters a lot on 5/10W TDP mobile processors, but matters much less on 45W TDP laptop processors.
- martin8412 6y agoHasn't it been a while since 45W TDP processors were common in laptops? My X395 uses a 15W TDP processor
- smabie 6y agoHow is the developer ecosystem going to fair? I would imagine a lot of tools don't work on ARM (or aren't regular tested on ARM). Moreover, I feel like it's going to be a big problem that the architecture you're deploying your code to is different than the one you are developing on. Who knows what kind of crazy performance differences/bugs there are between ARM and x86_64. Also, what about the audio/video/modeling software? I can't imagine that there's any support for ARM at the moment in that space. Also, is the Mac Pro going to switch to ARM? I'm not aware of an ARM chip that can compete with the super highend Xeons in the Pro. Having laptops run ARM and Pros run x86_64 doesn't seem like the best idea (also sounds like a lot of work on Apple's part). Of course, maybe this switch is going to create a high-end ARM space, allowing ARM to make inroads into HEDT and the server market. A lot seems unclear at the moment, but one thing is clear (to me atleast): there's going to be a huge fight over the next 10 years, x86_64 vs ARM. No one can possibly know who will win, but it's exciting to the say the least. I think we've all been a little tired of the x86_64 monoculture since the end of PPC.
- wyldfire 6y ago> I would imagine a lot of tools don't work on ARM A lot of open source code works well on ARM. But will we start to see some newly-discovered-but-latent arch-specific bugs, compiler bugs, undefined-behavior bugs-but-worked-on-x86_64 bugs? Yes, sure. The cool thing is that Win/ARM and Linux on arm are still very much the same OS as their x86_64 ports. Presumably macOS is/will be the same way. ARM gets less love precisely because they're not as popular for developer native workstations. But I wouldn't be surprised if that changes over the next decade.
- dewey 6y agoWouldn't it be similar to the PowerPC -> Intel transition or is there something that makes this more complicated? That one worked pretty well with the Rosetta emulation layer.
- wmf 6y agoLast time, Apple switched to the "industry standard" architecture with all the benefits that entails; now they're switching away from the (current) "standard".
- ngcc_hk 6y agoJust read the other piece about replacing mac by r pi. The potential is there. And with Apple control the chip ... it would be brutal.
- agustif 6y agoMy macbook has 2000 battery cycles, and thinking about acquiring. pi
- bit_logic 6y agoMaybe this rumor is only half right and it isn't what everyone thinks it will be. Instead of replacing x86, what if it's just Apple adding their ARM chip to the laptop? Basically just take the current MacBook and stick a iPad ARM chip in there. And maybe make the screen a touchscreen too. It would make iOS development much closer to the real thing. And for non-developers they can run iOS apps natively. So you get a Mac that can run both x86 and ARM natively. But if you try to use more iOS (ARM) apps you get really long laptop battery life since it's optimized for that. And x86 is there when you need to run more power hungry applications. Seems like the best of both worlds in a single laptop if they do this.
- scarface74 6y agoPeople thought Apple might be do the same thing when converting from 68K to PPC and PPC to x86. Apple would never do it. However, there were PPC upgrade cards for 68K Macs but you had to reboot to switch from 68K to PPC.
- oroup 6y agoAdding significant BOM cost, growing physical volume, reducing battery life, creating lots of complexity to get certain apps to run on one CPU or the other and the associated cache coherency issues? So that iOS developers can test their apps on a native CPU (But still plenty of differences like screen size, no cell radio, no GPS, accelerometers, etc) Seems dubious.
- ChuckNorris89 6y agoAll Macs already have an ARM chip inside them in the form of the T2 chip.
- jedieaston 6y agoBut that’s specifically for Secure Enclave work (disk encryption, biometric data). I don’t think they’d want to risk someone running arbitrary code there and breaking the sandbox. (The SEP is also separate from the A-series chip in the iPhone for a similar reason, IIRC).
- yusyusyus 6y agoFor my work, macs have never been really useful to develop on without additions. The whole "I can run virtualbox" and having a good out-of-the-box unixy setup is what has kept me coming back. Linux/others are not a realistic option as a daily driver for what I do. No x86, no virtualbox. No virtualbox and I'd rather just get (with much sighing, complaining, and general ill will) a windows laptop. I mean, the terminal is becoming slightly more useable in windows, right? And sometimes you just need to run a windows VM, so you need x86 virtualization. There are downstream effects to losing the "nerd" base and I suspect this move is a bad idea, but apple has a track record of pulling rabbits out of hats and knowing what really matters. Maybe this customer segment just doesn't matter.
- dangus 6y agoWindows has an ARM version.
- pottertheotter 6y agoThe thing I like about macOS over Windows when it comes to the terminal is that it's a native part of macOS and I don't have to monkey around with as many things. On my Macs, things aren't that much different compared to when I'm working on my Ubuntu server. I don't feel the same using WSL. It's not a seamless experience. Also, I've never found a terminal emulator I enjoy using on Windows. Maybe it's still way too early, but even the new Windows Terminal left me less than impressed.
- wonderlg 6y agoDoesn’t Apple already include an ARM chip in MacBooks with the Touch Bar? I have three feelings: 1. Apple will just enable the existing chips “today” and developers can ship ARM code to a sizable audience, with instant battery benefits. 2. Cheaper Macs will start dropping x64 next year and continue running only ARM code, maybe emulating x64 like Rosetta. 3. Pros will keep having both processors for the foreseeable future, similarly to how they have “dual graphics”, except that the OS will always run on ARM. We should keep in mind that Apple just dropped a swath of 32-bit software which means they aren’t afraid to do it again.
- Splognosticus 6y agoIndeed this would be the fourth time they successfully switched architectures. They went from m68k, to PPC, to x86. Apple is in a pretty unique position in that they make both their hardware and software ecosystem. It gives them a lot of flexibility that companies who just make generic Wintel systems lack.
- G4E 6y agoThere is a legal slowdown for emulating x86 (and x86_64 I beleive), because of Intel patents. That's why Microsoft's first attempt to ARM was such a disaster, with no compatibility with Windows' huge ecosystem. That's why there is no commercial toolsuit who offers x86 compatibility on other architectures. But maybe the situation has evolve ? Expired patents or a deal between Apple and Intel ?
- giobox 6y agoIt’s a nice theory but the the Touch Bar CPU specs are pretty well known at this point - if Apple had wanted to do this they would have designed the system differently. Supporting a different ISA on the same OS/Runtime is relatively “easy” in 2020 and doesn’t need such a sophisticated strategy - for 99 percent of developers this is going to be a one click recompile to different build target in their IDE. Push new binaries to App Store and done. By “easy” I mean relative to how ISA transitions have been managed in past. Apple are so big now that runtime mechanisms for x86 code, such as Rosetta during the PowerPC to x86 migration or hardware emulation on the 68k etc, just aren’t necessary this time around IMO. People will recompile. For sure we will lose some software that is too old to be recompiled by long lost authors, but I don’t think Apple cares. They already just killed 32bit app support with similar consequences. Remember today that your “arm” iOS apps work just fine in your x86-based iOS simulator in Xcode on an intel Mac, so access to actual ARM hardware isn’t a significant barrier at all to development for most.
- neonate 6y agohttps://archive.vn/qbMuX https://archive.vn/qbMuX
- mromanuk 6y agoAnd what about this other rumor? (Which is much more plausible). They could put everything T2, GPU and x86 in the same platform, bringing the cost down https://www.engadget.com/2020/02/07/apple-may-testing-amd-processors-internally/ https://www.engadget.com/2020/02/07/apple-may-testing-amd-pr...
- wmf 6y agoNot having x86 at all is even lower cost.
- monocasa 6y agoI've been saying this for a while, that a semi custom x86 (probably from AMD) makes way more sense. Those 8 Zen2 cores with 16GB with a very passable GPU in the next gen consoles show that it can be done for a remarkably low cost all things considered. Yes, Sony/Microsoft are probably taking a hit on those, and yes Apple would have to spend even more to get it running in a laptop form factor/TDP, but they also have MSRP headroom to make that happen with a decent margin. Even more out there idea (with literally zero proof, it's just a good idea, IMO): Apple buys Centaur, and gets an x86 licence. * Apple gets to have custom power efficient cores augmented by all the fabless firms they've acquired over the years. * Mac stays x86, so Intel wins a minor victory when the alternative was a major customer switching to ARM. * Intel wins a bigger victory because an x86 licence is effectively removed from products being on the open market. The great equalizer that is the end of Moore's law makes that licence sitting out there a long term existential risk for Intel. * Apple doesn't have a costly transition with the tail end of Moore's law meaning they don't have the same perf gains expected from the other transitions. * Apple also puts their hands on Centaur's newer inference accelerator IP. * Centaur's parent keeping them on life support gets a payout. Everyone wins except AMD (which is another win for Intel).
- philistine 6y agoTim Cook has said it: We believe that we need to own and control the primary technologies behind the products we make. So it would make no sense to trade Intel's poor schedule and performance for AMD's uncertain future performance. And aren't all x86 licensee prevented from keeping that license if they are bought?
- m0zg 6y agoI have to say, I'm not sure how Apple can pull this off. Mac commercial software is pretty sparse and crappy as it is. I mean, if I can't run the apps I use on a daily basis there (Adobe stuff mostly), it's a complete non-starter. Introducing another arch is not going to help matters there. If they try to pull in software from e.g. iPad, that's also pretty crappy. How many note-taking apps does anyone really need? And besides what few good apps iPad has, they won't work all that well in the desktop context. I guess we'll see soon enough. I doubt they're as naive as to believe that they can pull another massive arch switch without Jobs' reality distortion field, and without their current arch severely lagging (like it was in PPC->x86 transition).
- Closi 6y agoWell Adobe will definitely support the new architecture, it would be stupid for them not to. And additionally with the latest iPad becoming much closer to ‘Mac’ in terms of the browsing experience (eg with a touchpad) it makes total sense for Apple to start making some of their apps truly cross platform. Does the Spotify desktop app really need to be substantially different to the iPad app?
- m0zg 6y agoIt took them quite some time to start supporting Intel Mac last time.
- looping__lui 6y agoWhat I don’t quite understand in the discussions here is the hardware focus. No offense, but the libraries Intel is putting out there (IPP, MKL) for efficient parallel computing are really outstanding. It has been a fee years for me in the end-consumer high-performance market, but AMD chips would easily run 20% slower if you optimized the code w/ the Intel Libraries and OpenCL would Not get anywhere near. A similar thing happened w/ Nvidia and Apple many more years back; E.g., Apple dropping Nvidia; fair amount of rumors went around that Apple did that so Adobe would be less competitive if they had to rewrite their rendering engine (which they just ported to CUDA) and Apple could sell their video editing solutions with an edge (they have been hand tuned for a while of course...). Apple dropping Nvidia has been such a “non-customer-focused” bullshit decision. Not because the AMD hardware is bad - but OpenCL has simply been nowhere near CUDA. Same with Intel IPPs and OpenCL. But maybe that changed. The differences in performance, ease of use etc. have been mind-blowing back in the days for CUDA and IPP. Hardware alone isn’t gonna cut it. The machines are built to run software after all... Maybe that has changed or maybe nobody needs any parallelised compute intensive applications on Mac (research anyone, image and video editing anyone?). The fact aside that mayor software companies like Adobe et al. will probably have to staff entire departments for rewrites...
- sfifs 6y agoIn my data science org, virtually NO ONE joining new prefers MacBook Pros because of the lack of CUDA. Yes production workflows run on cloud and you can spin up notebooks on the cloud but having the flexibility of CUDA in your laptop for dev is just really high. People who joined with Macs are trading in for more powerful Windows machines
- _bxg1 6y agoI just bought a new 16" MBP earlier this year and I can't decide if it was the very best or worst time to do that.