Control freak, or reverse psychology?

One of the things that has had the tech blogosphere up in arms is the exclusion of certain technologies from the iPhone, specifically Java and Flash. There are those who insist that THEY MATTER, and that any device without them is Doomed(tm). (I seem to recall the same argument about pocket music players without WMA support, but whatevva.) There are those who think that they'd be nice, but not necessary. And there are those who are glad they're not being offered, and hope it remains that way. All three camps, of course, think the other two are insane.

There are some good political reasons for not having Java and Flash on an Apple device:
1) Java isn't really used anywhere else in the Mac ecosystem. It's *there*, but as someone who runs Java apps daily, let's just say that the rest of the Java development world tends to forget that Java is supposed to run on more than just Windows. (And let's not get into the puketacular UIs that come out of that realm.)
2) The iPhone has Cocoa. What need is there for Java, from the user's perspective?
3) Flash is proprietary. One of the biggest up and coming uses for Flash is to embed video in a webpage. I'm fairly certain that Apple might have some problems with that, given their huge push for ISO standards such as H.264 and MPEG-4.

With the advent of the iPhone SDK, it turns out that there's no technical reason why Java and/or Flash couldn't be ported to the iPhone. (I mean technical reasons why it *couldn't* be ported, not technical reasons why it *might not be a good idea*, such as battery life.) Sun announced last week that they plan to create a JVM for the iPhone, and today Adobe announced intent to create a Flash Lite installer.

However, if you look in the SDK EULA, you find out that one of the classes of applications specifically included is anything that runs its own executables, including plugins. Boom: no JVM or Flash allowed.

This has Sun and Adobe *pissed*. They are fighting mad, fighting tooth and nail to get their technologies on the iPhone, and goddamit, they are *NOT* going to let Jobs be right that they suck battery life, are slow, and are exactly the poor user experience he said they'd be.

In other words... if Apple succeeds in keeping Java and Flash off the iPhone, they really only hurt Sun and Adobe.

If Apple fails, and Sun and Adobe bring highly optimized ports to the iPhone... gee, Apple didn't have to put a dime into porting them, did it? Wow, that kind of failure really sucks.

Compare and contrast this with Java on MacOS X, where Apple finally got tired of the lousy JVM performance from Sun, and took it in-house, or Flash, which is one of the buggiest plugins for Mac browsers, is consistently a generation behind the Windows counterpart, and about 3x as slow.

Nicely played.

Control freak, or reverse psychology?

One of the things that has had the tech blogosphere up in arms is the exclusion of certain technologies from the iPhone, specifically Java and Flash. There are those who insist that THEY MATTER, and that any device without them is Doomed(tm). (I seem to recall the same argument about pocket music players without WMA support, but whatevva.) There are those who think that they'd be nice, but not necessary. And there are those who are glad they're not being offered, and hope it remains that way. All three camps, of course, think the other two are insane.

There are some good political reasons for not having Java and Flash on an Apple device:
1) Java isn't really used anywhere else in the Mac ecosystem. It's *there*, but as someone who runs Java apps daily, let's just say that the rest of the Java development world tends to forget that Java is supposed to run on more than just Windows. (And let's not get into the puketacular UIs that come out of that realm.)
2) The iPhone has Cocoa. What need is there for Java, from the user's perspective?
3) Flash is proprietary. One of the biggest up and coming uses for Flash is to embed video in a webpage. I'm fairly certain that Apple might have some problems with that, given their huge push for ISO standards such as H.264 and MPEG-4.

With the advent of the iPhone SDK, it turns out that there's no technical reason why Java and/or Flash couldn't be ported to the iPhone. (I mean technical reasons why it *couldn't* be ported, not technical reasons why it *might not be a good idea*, such as battery life.) Sun announced last week that they plan to create a JVM for the iPhone, and today Adobe announced intent to create a Flash Lite installer.

However, if you look in the SDK EULA, you find out that one of the classes of applications specifically included is anything that runs its own executables, including plugins. Boom: no JVM or Flash allowed.

This has Sun and Adobe *pissed*. They are fighting mad, fighting tooth and nail to get their technologies on the iPhone, and goddamit, they are *NOT* going to let Jobs be right that they suck battery life, are slow, and are exactly the poor user experience he said they'd be.

In other words... if Apple succeeds in keeping Java and Flash off the iPhone, they really only hurt Sun and Adobe.

If Apple fails, and Sun and Adobe bring highly optimized ports to the iPhone... gee, Apple didn't have to put a dime into porting them, did it? Wow, that kind of failure really sucks.

Compare and contrast this with Java on MacOS X, where Apple finally got tired of the lousy JVM performance from Sun, and took it in-house, or Flash, which is one of the buggiest plugins for Mac browsers, is consistently a generation behind the Windows counterpart, and about 3x as slow.

Nicely played.