• 98% of language specs • 94% of core class specs • JRuby 9.2 (master) compatible with Ruby 2.4 • Features mostly complete • Working on next-gen optimizations
Rails • We expect similar ratio for mysql, pgsql • No version checks; support for one Rails version at a time • w.x.y.z: w.x will match Rails, y.z will be our versioning+security • Working with Rails to increase amount of shared code • Ideally, our extra code could just go in rails/rails
for the server; see also ratpack • Most deployers work (capistrano, etc) • Warbler, torquebox, and other tools for all-in-one executable jar • Java-style • Torquebox for full-stack env (messaging, scheduling, clustering and more in the box) • Warbler for existing Java servers • Full set of Maven utilities for heterogeneous apps
pauseless • Built-in tools for analyzing GC, JIT, thread, IO, heap • Built-in remote monitoring via JMX • Dozens of tools out there for profiling, management, and more
JIT compile to JVM bytecode • Use invokedynamic to make dynamic calls fast • Optimize Ruby before sending it to bytecode • Start utilizing new Graal JVM JIT
update wiki, docs • Respond to questions • Mailing lists (jruby, ruby-talk, ruby-dev, ...) • Social media (Twitter, IRC, Gitter, ...) • Get out there and talk to people!
Growing "kernel" of Ruby code • 'date' ext is just Ruby calling a Java date/time lib • Reduce the Ruby to a “bite size” test or spec • Implement fix or new feature in Ruby • Working code first, perf concerns later