Talk:Java: Difference between revisions
(+phoneMe) |
(+OGI) |
||
Line 18: | Line 18: | ||
=== Libraries and coding frameworks === |
=== Libraries and coding frameworks === |
||
''just supporting a JVM allows support of all languages currently supported; Scala, Python, JRuby...'' |
''just supporting a JVM allows support of all languages currently supported; Scala, Python, JRuby...'' |
||
== OSGI == |
|||
Remote fetching of functionality, allowing that to start/stop services and export this. You can manipulate dependencies between them... including calls out to find the start/stop routines. Talking to CDC about how to make lightweight apps and use cases (and libraries?) work together in a 'just in time' environment. |
Revision as of 00:00, 6 July 2007
J2ME and JavaME
Now called JavaME... all this work on the language since the GPLing of Java has gotten Sun to realize how bloated their version is.
CDC and CLDC
The CDC is ~10M that implements all the key parts of Java. Getting an existing Java package (that might use Swing, for instance, which is not in CDC) to run under it should be much much faster than a port to Python. CDC implementation: phoneME.
GCJ and Eclipse
GCJ can compile eclipse. It's an AOT rather than a JIT... it makes hacking less interesting, but a crosscompiling toolchain could be most useful.
SWT
Eclipse is built on this. Many people bring in SWT bindings for their platform (like GTK on Linux).
Existing applicationsets
Educational packages
see the main page
Libraries and coding frameworks
just supporting a JVM allows support of all languages currently supported; Scala, Python, JRuby...
OSGI
Remote fetching of functionality, allowing that to start/stop services and export this. You can manipulate dependencies between them... including calls out to find the start/stop routines. Talking to CDC about how to make lightweight apps and use cases (and libraries?) work together in a 'just in time' environment.