Yes. Truffle aims to become a production-quality system. A successful research project should ultimately also advance the state of the art of what is used in production. We are well beyond the initial exploration phase for Truffle and focusing currently on stabilisation. There is a Truffle branch in the JRuby open source base on github (more info here https://github.com/jruby/jruby/wiki/Truffle or here http://blog.jruby.org/2014/01/truffle_graal_high_performance_backend/). There are open source projects using Truffle that currently develop a prototype for R (https://bitbucket.org/allr/fastr), one for Python (https://bitbucket.org/ssllab/zippy), and one for Smalltalk (https://github.com/smarr/TruffleSOM). We are also working on JavaScript. This makes us confident that we can support a wide range of languages.
- thomas On 29 Aug 2014, at 11:06, Patrick Wright <pdoubl...@gmail.com> wrote: > Thomas, > > > > Thanks for this detailed analysis on the current status and proposed future > work for invokedynamic. Can you also add some comments on what you believe > the advantages and disadvantages of using Truffle instead of invokedynamic > for implementing dynamic languages on top of the JVM are? > > Along those lines, could you tell us if Truffle aims to be a > production-quality system? I had thought - perhaps incorrectly - that it was > a kind of research project, like (as I understood it) the Maxine VM was a few > years ago. > > Thanks! > Patrick > _______________________________________________ > mlvm-dev mailing list > mlvm-dev@openjdk.java.net > http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
