On Oct 7, 12:57 am, "Kevin J. Butler" <[EMAIL PROTECTED]> wrote:
> RobG wrote:
>
> > On Oct 4, 7:20 am, "Kevin J. Butler" <[EMAIL PROTECTED]> wrote:
> > [...]
>
> >> When... Sun deliver versions of ... Java that let Apple control the
> >> applications delivered to the iPhone, Apple will let it happen.
>
> > The lack of Java on iPhone has nothing to do with Sun, the iPhone
> > simply has no JVM. Apple doesn't supply one and there's no 3rd party
> > JVM for it from Sun or anyone else.
>
> This is incorrect.
I was correct about it not being Sun's fault. ;-)
> http://java4iphone.com/all-news/all-news/tutorial-install-java-on-the...>
> Even if there was, you'd either
> > have to jail-break your phone to install it or get Apple to agree to
> > install it (by App Store or software update).
>
> Yes, you have to jailbreak the phone. As I said above, it doesn't "let
> Apple control the applications delivered to the iPhone"
Apple could likely build a JVM that did just that, although it might
not get Sun's approval. I don't see that Java differs from any other
programming language in that regard.
[...]
> As I said, the issue is not technical. It is completely a matter of
> control - Apple really /really/ wants to control the iPhone application
> market monopoly and use it to strengthen their Mac OS market monopoly.
> Anything that delivers applications by channels other than via Apple is
> thus a Bad Thing.
I think they are trying to apply their iTunes strategy to iPhone, but
I doubt that it will succeed. The music delivered on iTunes is mostly
professionally produced and of very high quality. The App Store is
quite different - pretty much anyone can put up an application and
there is only minimal quality control (there is a good business
opportunity to setup an App Store advisory service to let people sift
out the applications that are worth using and provide sound advice on
their capabilities).
Most of the issues Apple were trying to avoid by not supporting Java
have occurred anyway, so the strategy failed. The only effect it’s
having is that applications must be written specifically for iPhone
using the SDK and therefore it’s more difficult (but not /that/
difficult) for developers to support multiple platforms.
So to me it boils down to support costs and performance. You say
performance would be OK (I’ll take your word for it, I don’t know) so
what’s left? Of course Apple may have some completely different
reason, but I’m out of sensible ideas.
--
Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---
