Engadget Mobile, still magenta and proud, just sat down for a chat with Sun Microsystems CEO, Jonathan Schwartz, and naturally, primarily, the topic turned the baby leopard in the room, the iPhone:
So I'm curious, what kind of phone do you carry?
As of yesterday, an iPhone.
Butofcourse. Any guess as to the first thing Schwartz wants to do with it? No, not watch a day-and-date movie. No, not browse the real internet. No, not Google locate Scott McNealy spirit (what, to obscure?). He wants:
...the Java platform
Sigh. While Java does run on almost every other phone but Apple's Cocoa powered platform, enabling everything from the Blackberry OS, to the carrier crapplets everyone loves to hate, does the iPhone really need double-layered SDK? And doesn't Apple's iPhone SDK user license agreement specifically forbid the old code-within-a-code play?
Quoth the Schwartz:
Well I think the only difficulty will be what Apple presents through its EULA. But I think that I think EULA is a bit of an oxymoron to me. They're end users, they have the freedom to choose what they'd like to do, so I think we are going to leave it up to users to decide how they want to use the technology
Apple, of course, does use the Java-based WebObjects for it's Apple and iTunes stores, so my guess isn't that they're adverse to it in theory, they just want to use it where it makes sense -- web and server based applications that benefit from code portability more than performance. They're just not keen to have it on their phone, where it may only make the kind of sense that doesn't.
Personally, I love it whenever needlessly Java-based apps spin up for interpretation, downgrading both performance and my sanity. Any programmer who cares about the device, performance, and power will almost certainly WANT to write as close to the metal as possible, at that will mean porting to Cocoa Touch.
What do you think?