Applications have to be built to run on ARM. People own existing applications for x86, they won't work... not all applications will be built to run on ARM.
There are still compatibility issues.
ARM+ Windows 10 is not a magic bullet.
ARM's potential power isn't the main issue, if it ever matches or outperforms x86 - losing the ability to run Windows or Linux apps without emulation however would be a huge loss.Recall few thought ARM would be good for tablets or phones initially.
Any app uploaded to any of Apple's app stores within the last year (or was it a few years ago now?) was uploaded in an intermediate format, from which Apple can compile it to any final architecture that they want.
So the transaction should be completely seamless for any app updated on the app store since then.
Any app which is still being compiled for OS X but not put on the app store will have a new compiler target added in Xcode (I think everything is compiled through the Xcode tools these days... pretty sure even things like JetBrain's AppCoda rely on Xcode's command line tools to do the actual compilation.)
I would bet that most apps not distributed through the app store actually rely on Python, Ruby, a JVM, or some other interpreter though. Those would have a seamless transition - just need the interpreter to be recompiled with the new target. All the major interpreters already work on ARM and are still actively maintained, so no trouble there.
Apple could offer an emulator like they did with Rosetta for transitioning from PPC to Intel. But I don't think that's even necessary this time around.
Hmmm... I'm realizing right now that the iMac might be the first and only new Intel Mac that I ever buy (the MBA and MacMini each came from family members who weren't using them anymore.)
That's the thing. The A9X isn't intended to calculate SHA1 hashes all day. The A9X is intended to wake up, calculate a SHA1 hash (used for SSL, iirc) really quickly, and then get back to what it does best-- napping. The result is a computer platform that's good for browsing facebook (without too much perceptible lag), for many hours on end.
This is not what you want in an iMac. This is not what you want in a Mac Pro. And it may not even be what you want in a Macbook Pro. If you look around, you'll probably find lots of critics deriding the retina MacBook as "the slow mac".
And suddenly, just because an iPad Pro turns out to beat 'the slow mac" on a methodologically suspect benchmark, people are ready to dump Intel? Why-- because ARM appears to be "catching up?"
ARM's potential power isn't the main issue, if it ever matches or outperforms x86 - losing the ability to run Windows or Linux apps without emulation however would be a huge loss.
I don't understand this. The vast majority of people buying Macs now don't know what processor is in it, they just want to know if the emails, and the internets, and the facebooks will work. And those activities really don't need an Intel processor. If Apple releases a platform that can "Facebook" as well as they currently do, there's no reason to believe that sales will fall by a significant amount.
Sure there are those that NEED to virtualize, but I'd imagine there's more mac users on using Facebook in a given month than there are Mac users that utilize virtualization by a wide margin.
[doublepost=1460431553][/doublepost]
It's a starter, it will just leave certain small segments of the mac using universe behind. For every 5 people who can answer "No" to the question "Would you purchase the next Apple device if it didn't utilize the x86-64 instruction set?", there's 100 that will answer, "I don't know, but I guess as long as I can still get to Facebook and watch cat videos on YouTube..."
Additionally, ARM has nothing to compete with Xeon at the top end.
Conversely, that means intel have 15-20% margin they can drop their pants on if they want to keep apple's business, which will further increase the power: price advantage in intel's favour.
And that's IF Apple decide to entertain the idea of ARM based Macs. Which i reckon would be suicidal for the mac market. The fact that the mac runs x86 is a huge reason why i have one of them in addition to iPads.
No, they could not have. The CPUs going into the 13" MBP and the MBAs aren't available in Skylake versions yet (the one going into the MacBook One are though, as the ones going into the 15" MBP).
Xcode already compiles for ARM and Intel. It's not a stretch to say that Apple could solve that problem with a setting in Xcode that allows you to recompile your code to ARM. A few compatibility checks later, upload that to the App Store, no emulation needed.
[doublepost=1460447583][/doublepost]
"All of their software" for very many means Safari, with the addition of possibly Mail. There's already ARM versions for those. Maybe for some, it's iWork or the former iLife apps, which already have ARM versions (UI can be tweaked). Those apps they bought from the App Store? Apple could tell developers that everyone using Xcode has to recompile with the ARM trigger enabled before they release their next update.That covers a huge swath of the current user base. Some will be left out, but unfortunately it's likely to primarily be those who know what x86-64 means.
I would be surprised. The x86 change allowed them to gain many customers who would have never considered macs otherwise (myself included). If they switch to ARM, I'm going back to PCs.
I think that 99% of the 3 billion don't need to be coding on iOS. Most of them just need email, word editor, spreadsheet, browser, movies, pictures, music, apps. And a large portion of those people only need basic capabilities in each of the categories i just mentioned.
Now where is your paycheck![]()
I said hello to a Dell XPS 15 over the weekend. We had a good run Apple.
I always thought that the X in OS X was for the X86 architecture, although many said it was because Uni*.
How is it? That laptop looks killer. Almost bought one for my father, matter of fact.
When you see a Mac story on the FP but it's just a technology brief![]()
Thanks, good info to know and it does seem like they are doing what's possible to become agnostic so if the need arises, it's more of a when question than how.Xcode introduced bitcode a few months ago.
Now you can submit to the app store an intermediate representation of your binary, not compiled for a specific architecture.
If Apple makes the "switch" a simple recompile via Xcode, it would be even easier than when the development tool of choice was CodeWarrior. Apple may have been dying but there were a LOT of applications for Motorola processors. It wasn't as easy a decision as you make it sound.That's not the point.
Unlike the old Motorola CPU days (don't forget Apple was dying) now there is a massive and deep base of programs in OS X Intel and to switch it to ARM is huge.
Apple isn't going to stand by and allow this for long. They had always wanted to control as much of the computer as possible. The main reason for going with PowerPC over Intel years ago was they could control the processor cycle and not be "just another Intel machine". They switched to Intel because PowerPC stagnated and could not keep up with Intel advances. We are seeing now that Intel is not able to keep up with the type of mobility and power efficiency (and power) that Apple requires. So I do believe they will do it again. This time, they will move to their own chips and completely control the platform outside of manufacturing.
The A9X is faster than my Macbook Pro Retina 13" (Late 2013). Sure that's a 2.5 year old machine. But the fact is that it's still a decent machine. If Apple keeps on trajectory with performance enhancements and can squeeze another 50% into A10X, then I don't see an issue moving to that as a platform for OS X, especially with the insane graphics performance its already showing. The iPad Pro is a beast in a box that is NOT being used to its potential. I think the plan is Apple has some upcoming software (always Apple's strong point) that will take things to the next level. Perhaps the ability to compile iOS apps to a Mac running on an A10X processor.
If you look for some of the old Keynotes, that's exactly how it worked. For all those developers who had used Xcode for their development, there was a button in the interface for PowerPC or Intel or both. A big deal was made of the fact that application developers were able to get a working version almost immediately and then just spend time tweaking some of the areas that didn't turn out as efficient as they would like.Is that how the transition from PowerPC to Intel worked? A few compatibility checks and everybody's apps had Intel versions?