A simple rule to follow right now: never trust someone who's selling an AI coding product to tell you how great AI is at coding.
It sounds like my experience has been similar to yours. I have found a few places where agentic coding produces pretty good results.. generally very small patches that could have been written by anyone. I give the tool credit for finding small bugs that nobody noticed before.
On the larger or novel tasks I've thrown at these models, including some of the top tier options, the tools have either produced incorrect solutions, solutions written in a very inefficient way, or solutions that actually introduced more problems. I've taken some of these same challenges to other AI experts as who couldn't believe the tool failed. None of them were able to get good results either.
Everybody is desperate to carve out their slice of the AI Gold Rush right now before it all condenses down and developers realize they can't give up all agency to coding tools trained on the great mass of garbage that's out there. If at some point these tools truly do make developers 10x more efficient, they'll naturally get adopted. Hype chasers and product marketers are not the ones to listen to right now.
Let's take a look at JRuby's startup time journey, all the way up to using JDK 25's AOTCache and Project Leyden features coming to a JDK near you soon.
JRuby 10.0.2 is released! This is a small release to fix an ArgumentError regression in JRuby 10.0.1 plus a few other small fixes. Recommended upgrade for all, but let us know if you run into any issues!
We have just released JRuby 10.0.1.0, our first update to JRuby 10! There's dozens of patches including full support (finally) for Zeitwerk and a bunch of Ruby 3.4 language fixes. Upgrade today and let us know how it goes!
It's finally here! JRuby 10 has been released with support for Ruby 3.4 (including 3.2 and 3.3 updates as well). Minimum Java version has been bumped up to Java 21, allowing us to support more modern JVM features. Check out the release notes and begin your migration today!
We have all of the right tooling created to fetch jars from maven but no good tutorials on stitching it all together. Clearly that is step we should document better.
And for those following along, we keep the jbang configuration updated with every release so you know you're getting the most recent version.
Very excited to see folks trying this out! Please get in contact with us (jruby team, either on social media or our matrix channel) if you have any troubles.
A very nice article by Paul Krill! We are looking forward to this release and having feature parity with regular Ruby while also updating JVM support for modern features. You can get expert support for JRuby projects, including migration from CRuby and third-party gem development, from Headius Enterprises.
Part one of a series exploring the use of OpenJDK Project CRaC (Coordinated Restore at Checkpoint) and CRIU (Checkpoint and Restore In Userspace) to improve the startup of JRuby
A quick look at the big projects coming soon for JRuby. Ruby version updates, new optimization work, and integration with modern JVM features like Loom, Panama, CRaC, Leyden and more.
It is unfortunate, to be sure, and I strongly disagree with Red Hat's decision to cut important projects like JRuby.
When we joined Red Hat in 2012, it was the most exciting career move of my life. A company I had long respected for its dedication to and support of OSS... this was a place I could finally do good work for the community for the rest of my career.
I was still cautiously optimistic when IBM bought the company, since for several years it seemed like the status quo would be maintained; Red Hat was very successful at driving new revenue to IBM, and investment in OSS continued apace. I guess being the most profitable division of IBM was not enough.
I wish my remaining friends and colleagues at Red Hat the best of luck.
I'm still very proud of that talk and it's one of two we decided to include on the Headius Enterprises "About" page here: https://www.headius.com/about
I hope I can return to Carolina Code Conference next year to share my experiences going independent with JRuby!
It sounds like my experience has been similar to yours. I have found a few places where agentic coding produces pretty good results.. generally very small patches that could have been written by anyone. I give the tool credit for finding small bugs that nobody noticed before.
On the larger or novel tasks I've thrown at these models, including some of the top tier options, the tools have either produced incorrect solutions, solutions written in a very inefficient way, or solutions that actually introduced more problems. I've taken some of these same challenges to other AI experts as who couldn't believe the tool failed. None of them were able to get good results either.
Everybody is desperate to carve out their slice of the AI Gold Rush right now before it all condenses down and developers realize they can't give up all agency to coding tools trained on the great mass of garbage that's out there. If at some point these tools truly do make developers 10x more efficient, they'll naturally get adopted. Hype chasers and product marketers are not the ones to listen to right now.