This would be a big but expected jump, sending many developers back to the drawing board.
Expected - how so?
This would be a big but expected jump, sending many developers back to the drawing board.
Its a different version of windows because its on a different chipset. Today's applications for OSX would not work on an ARM based Mac because they're not compiled of run on a different CPU. OSX would need to an emulator, much like they did when they went to PPC to Intel.
Microsoft did not create a different windows version, but rather create a windows version to run on ARM. Apple is rumored to create an OSX version that will run on ARM
This is the exact same thing that MS is doing, running a copy of their OS on a different chipset, apps have to written/compiled for that chipset and it produces different binaries.
I have to believe an ARM based Mac is set to be a low end product and they're not dropping Intel altogether - that would be insane.
And here we go back to Windows!
There's been a few rumors of apple moving along to an ARM architecture, at least for one model. I don't understand it, look at the failure of the windows rt. I'd avoid it like the plague.
Most of your work is apparently still in the stone age.As much as I like OSX, most of my work still requires windows, so if they switched to ARM, I'd be switching back to PCs
I did read it, and I'm not sold that its a trivial move for developers since the cpu structure is so different. The same thing was said about PPC to Intel early on that developers only needed to cross compile and it would work, but that was not the case.Well, did you read all the stuff I wrote above the part you quote? As it is, cross-compiling existing Cocoa applications to ARM should trivially work for most of the apps. You don't need an emulator. You also don't need a different version of the app for each platform, because OS X allows you to have native code for different platform in the same binary (the universal or fat binary format, which they have successfully used with the PPC and then with x32 to x64 transition).
Most of your work is apparently still in the stone age.
But Windows is rooted in the PC era.
The world is moving on to the post-PC era.
Does Apple need to accommodate people who are tethered to an increasingly anachronistic method of working? Or should Apple concentrate on the future?
Versions of Office and iWork already work on ARM processors...versions that are good enough for the vast majority of users, versions that can and will be improved in time.
Increasingly, people are moving to cloud based services and apps...where the processor is irrelevant.
If ARM processors can meet 99% of the needs of 99% of users, then the PC era really is dead.
But Windows is rooted in the PC era.
The world is moving on to the post-PC era.
Does Apple need to accommodate people who are tethered to an increasingly anachronistic method of working? Or should Apple concentrate on the future?
Versions of Office and iWork already work on ARM processors...versions that are good enough for the vast majority of users, versions that can and will be improved in time.
Increasingly, people are moving to cloud based services and apps...where the processor is irrelevant.
If ARM processors can meet 99% of the needs of 99% of users, then the PC era really is dead.
The 64bit Dual Core A7 running at 1.4Ghz gets around half the geekbench score of the dual core i5 in the MBP. If they use a quad core it would be on par, then if they are to use 4-8 of them, it will be 4-8X more powerful. That has to be enough extra power to real time translate Intel processor applications to run on ARM would it not?
So if I understand your point, apples to apples, dual core A7 is 50% slower then a dual core i5 (in that specific benchmark), adding more cores will make it as fast as a dual core i5?
I'm not seeing the logic, throwing an quad core or octo core processor to compete against a dual core intel CPU doesn't seem to make sense. Plus the speed increase is not linear, more 2 more cores does not make it 2 times faster, 4 more cores makes it 4x faster.
So if I understand your point, apples to apples, dual core A7 is 50% slower then a dual core i5 (in that specific benchmark), adding more cores will make it as fast as a dual core i5?
I'm not seeing the logic, throwing an quad core or octo core processor to compete against a dual core intel CPU doesn't seem to make sense. Plus the speed increase is not linear, more 2 more cores does not make it 2 times faster, 4 more cores makes it 4x faster.
If the processor helps to sell the machine, then yes, Apple should keep Intel.
I don't think its any coincidence that Apple Computers sales started to excelerate after Apple went Intel.
Still too early to move to Cloud services for apps etc - firstly, limited available ( how many of your favourite desktop apps have web versions? ), and secondly, too unreliable with security concerns.
Many companies aren't moving due to security and reliability issues. They'd rather keep their data local to their organization.
A long way to go until PC era is finished.
Adding cores does not cause a linear increase in performance. The application needs to be able to written to take advantage of high cores and I don't most apps do. I think its overly simplistic to think you can double the core count to equal an intel cpu.But I'm sure that by doubling the core count (while still having the single threaded performance so high), as well as having 8 of them running together will well outperform the dual core i5 in the 13" MBPr.