Goals for 2019

• Release RingoJS 2.0
• Encourage our users to take on with new Java 9/10/11 APIs like java.time, java.net.http (the new HTTP client), unmodifiable collections, or the new process management.
• Update dependencies
  • Jetty
  • Rhino
• Finalize adaptions for Java 9 and upcoming Java releases
• Replace the ringo/httpserver with grob/httpserver
• Stay a solid and stabilized project without any big breaking changes at the core

Non-goals for the future

• Replace Rhino with GraalVM, Nashorn or any other JVM-based engine
• Major changes in the modules
• Modififcations of the module loader / resource management

Overall project status and outlook

In the last years the development of Ringo settled down at a low, but continuous rate. We see it as a solid JVM-based platform to develop and run large scale web applications. Our top aim is to stay solid and predictable, without any major changes. There is no intend to move from the Rhino JavaScript engine to any other alternative. Though, we will follow the updates of Rhino and Jetty. Since Jetty has easier HTTP/2 support, this will also reflect in Ringo.

Back in early 2008 when Ringo emerged from Helma, it hasn't been clear which server-side JavaScript platform will succeed (and Node.js came on the scene mid-2009). We had a vivid community around CommonJS which multiple interesting runtimes and frameworks. Though, today we face a dominant runtime with Node.js and the npm ecosystem. Instead of comparing with this Goliath, we will continue a separate and independent way. We will improve our small set of high-quality packages like stick and sqlstore, but keep Ringo’s core modules stable and API-compatible.

In the long run, we will see in Ringo an easy to maintain and deploy JavaScript runtime evolving together with the Java platform and its ecosystem.