Linked by Kroc Camen on Thu 28th Jan 2010 17:29 UTC
Web 2.0 Wolfire writes: "Today, Apple announced the new iPad and humbly claimed that there will be a "gold rush" of native apps for the App Store. Sure, but what I find more interesting is that Apple also ironically created the most promising open web app platform, which may eventually undermine the App Store itself. [...] The iPad is the first mainstream device which combines all of the following factors: reasonably powerful hardware, a (potentially) huge user base, a mature WebKit implementation, and constant 3G internet capabilities. All the dominoes are in place, and I think that the iPad will knock the first one down."
Thread beginning with comment 406500
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Dont forget Java too.
by siimo on Thu 28th Jan 2010 19:01 UTC in reply to "RE: Dont forget Java too."
Member since:

I think he was referring to desktop Java applications Kroc.

Reply Parent Score: 3

RE[3]: Dont forget Java too.
by Kroc on Thu 28th Jan 2010 19:09 in reply to "RE[2]: Dont forget Java too."
Kroc Member since:

Adobe are making Flash Pro CS5 compile Flash into a native (but essentially ugly) application to be force fed through the approval process. Could Java do the same?

Apple’s gateway policy is a different kettle of fish to discuss. A kettle that doesn’t exist in the web browser (if you excuse no-plugins).

Reply Parent Score: 1

RE[4]: Dont forget Java too.
by Lunix on Fri 29th Jan 2010 01:52 in reply to "RE[3]: Dont forget Java too."
Lunix Member since:

There are three options. Not good options, but options if you want to devote a lot of time.

The flash compiler uses llvm. llvm isn't a compiler, it's a low level virtual machine which can be compiled (or JITed) to a bunch of real architectures (including arm, x86, ppc, alpha, .net, etc). llvm and java vm are both documented (and open source), so in theory a jar file could be converted to llvm and compiled to arm (or another target). Of course it's not that simple since jvm is stack-based and llvm is register based and much lower level than the jvm, but it could happen.

GCC now includes a java compiled which can (optionally) compile to native code. There's also an llvm-gcc fork which compiles to llvm code. How about marrying the two up? Last I checked (which was a few years ago), the gcc jcc used its own backend and I don't think llvm-gcc supports java but if you switched the jcc backend to use the standard backend it might work.

The third option is using get to compile your java to a javascript web app.

Reply Parent Score: 1