Hi, Exactly.I suggested additionally that if it avoids patent problems, alternative bytecode could be used instead (like Dalvik's, since it's already widespread) as long as that doesn't block performant support of non-Java languages on the VM - while reusing as much of Harmony's existing guts as possible. Also, I think that if an open strongly-typed Java-like language were available on a widely-ported performant VM, it would be a great alternative to C#/Java and a step beyond Vala for Linux desktop/embedded programming.
What do people think about desirability and feasibility? - Would moving to Dalvik or other bytecode be useful? - Any reason why there would be insurmountable problems or poor performance running both a reference strongly-typed language and dynamic languages on such a VM? - Could an OSGi-like system be used to allow a slim set of runtime classes to be deployed for specific purposes like running e.g. a Python runtime on top? - Java could be the reference strongly-typed language initially if Apache can find a way of defining clearly what functionality is supported, probably by comparison with jdk 5/6. Then it can either shadow Oracle's JDK or take a community-led direction - maybe be replaced by another language later. - In the short term, could Harmony be released as it is, certified only for its ability to run the runtimes of a set of VM languages like Python and Ruby? Its class library implementation is surely solid enough. The bytecode output of the compiler could be changed later to match an updated VM if needed, perhaps with a temporary intermediate step, after the corresponding work on the language runtimes. Paul