If you see the value in having a strong, independent JRuby project, now is the time to step up and help ensure its future. JRuby needs you and so do I!
If you’re interested in how we got here, Charles did a great talk on JRuby’s history, origins and future last year.
I hope I can return to Carolina Code Conference next year to share my experiences going independent with JRuby!
I am not a ruby developer and even though I integrated it don't know anything about its internals. I am guessing if JRuby goes away GraalVM which supports Ruby will be its replacement?
JRuby runs on all JVMs with or without Graal, where the GraalVM languages are tied to that runtime. The design of those languages also incurs heavy startup, warmup, and memory footprint penalties even greater than that of JRuby or the JDK itself, and those problems are not easily solvable.
JRuby will never go away, and as long as I have a say in it, development will continue full speed ahead. We are tackling some of our long-desired optimizations now, have near parity on Ruby language features with the unreleased Ruby 3.4, and we're very excited for the future of the project.