How would the whole system work now? Simple. Doppio – Java Virtual Machine written in TypeScript – is the default Machine for JavaPoly.js. The new library can operate with several JVMs; yet, if there is no Virtual Machine installed, it falls to Doppio – this is the main way for Poly to work on any computer regardless of Java being installed or not.
According to project developer Jim Sproch, their primary goal was making web development in Java a lot easier. But the JavaPoly project is expected to grow into something even bigger shortly. It is planned to enable the whole host of JVM languages to work in a browser without any additional applets, even Scala and Groovy. Basically, any language would now be available through JavaPoly – you will be able to use Python through Jython.
Working on Chrome and Firefox plugins for JavaPoly.js, developers assure that new library would work fine in any browser. But it would be much faster for those having native JavaPoly support. JVM plugins API standardization is still in progress, and Sproch claims it is exceptionally advantageous for browser makers.
What else would JavaPoly.js change? Native browser support would put standard JVM onto a whole new level of performance. It would guarantee better performance compared to browser’s JSVMs.
Java was created as a stable language with well-built infrastructure and support for various features like shared memory and locking primitives, type-checking, etc. It had the whole team of engineers working to make it perfect and suitable for numerous applications.
The early beta stage of JavaPoly.js is still in progress, and the library will be available to the public when developers feel the API is stable enough.