Linked by Thom Holwerda on Sun 21st May 2006 23:20 UTC
Apple Did Apple make a mistake by switching to Intel? We may never know, but Apple had more options than has been previously reported, The Register can exclusively reveal. A chip start-up that created a high performance, low power processor compatible with existing Mac software had been working closely with the computer company for many months. "PA Semi was counting on that deal," said one source. "They had lots of guys walking around in a daze when Apple went to Intel. They had no idea that would actually happen." Ars's Hannibal, criticaster of Apple's reasoning to switch to Intel, also expressed his thoughts on this issue.
Thread beginning with comment 126967
To read all comments associated with this story, please click here.
dsmogor
Member since:
2005-09-01

Apple already support JAVA to great extent, so isn't your dream already kinda... fulfiled?

Reply Score: 1

Captain N. Member since:
2005-07-07

Not really just yet. Apple still doesn't put it's weight behind the idea by making parts of its OS use Java bytecode, like they do when they jump architectures as one example.

They have also switched their entire product line to the new architecture, where if they were going to aggressively support the architecture independant angle, they might have emphisized the Java bytecode a bit more, and kept the RISC architecture around for a while longer along side Intel.

Of course there are reasons to market the switch, even if they do decide later on down the road to push the independance angle, such as appeasing the darn media, who probably wouldn't understand the value of architecture independence. The idea is way outside of the norm, but could definately be called "thinking differently".

Reply Parent Score: 1

Captain N. Member since:
2005-07-07

After thinking about it, there are couple of things that would have to happen. Something like being able to compile Cocoa apps written in Objective-C and many other languages into Java bytecode would be necessary (which off the bat makes Mono seem like a better choice, but if I'm not mistaken, Java has similar language independance which could be made more prominent - switching XCode to Eclipse wouldn't hurt either).

Also, Java has it's own brand presence, I would think Apple would want to create it's own branding for whatever layer they put on top of the Java bytecode (or/and Mono - though Java stands in better contrast with Microsoft's .NET), and attempt to play down the underlying architecture (in the marketting, there's no reason to play it down in dev circles), although the thought of developing with Cocoa Beans, or Mocha Latte isn't so bad, if a bit cheezy. :-) For the performance criticle apps, make sure to always mention that Universal Binary thingy.

And if Intel doesn't like the idea of competing with other architectures (actually, this would provide a way in for their Itanium line), I'm sure AMD would be willing to help out.

Reply Parent Score: 1