By now you’ve heard the news: Tom Enebo, Nick Sieger and I will be joining the Engine Yard team to work on JRuby! We’re very excited about this opportunity and we’re looking forward to a bright future for JRuby and the community.
But why Engine Yard?
Engine Yard is, by almost all measures, the leading Ruby and Rails company in the world. They’ve literally written the book on how to make Rails deploy and scale easily, and if you have a tough Rails infrastructure issue, they’re the company you talk to. But in order for Rails to penetrate the large organizations of the world, many of which run Java in some form, JRuby is often the answer. So out of JRuby, Engine Yard and the Ruby community get a broad new landscape of opportunities.
For JRuby, the move to Engine Yard means we’ve got a dedicated Ruby and Rails company backing our project. We’ve always believed in Ruby and Rails, but have long realized there’s more we need to do. We need to finish support for the newer Ruby versions like Ruby 1.8.7 and 1.9.1. We need to build out the “last mile” of JRuby’s Java integration logic, to allow seamless two-way integration with Java frameworks and libraries. And we need to work with Rubyists to reach out to the Java community, to expand Ruby into a much larger world. All of this will be easier to do with Engine Yard backing us up.
So, what does the future hold for JRuby?
Well there’s the aforementioned work on Ruby 1.8.7/1.9.1 support, which is already very far along. We’re looking at making a move to 1.8.7 for base compatibility in JRuby 1.4 right now, and will start filling in the remaining 1.9.1 bits very soon. I also mentioned Java integration work; our goal is that JRuby will become a “first class citizen” on the JVM, so you can swap out any piece of Java for a bit of Ruby with as few penalties as possible.
Already we’ve begun exploring how to make libraries like Hibernate, JAX-RS, and many more integrate well with JRuby and Rails. Of course we already have excellent performance characteristics, but that work will also continue. And we plan to work very closely with the Rails core team to ensure Rails fits seamlessly into classic and modern Java platform stacks.
As far as Engine Yard goes, we’ll be working with the Engine Yard Cloud team to make sure our JRuby support is top-notch, and we’ll be exploring possible paths for JRuby’s future. We want to deliver a full set of cloud, hosting and support options, and will be talking to users and studying alternative platforms to figure out what those options should look like.
Ok, I’m hooked… how can I get started with JRuby?
Your first stop should be either my previous Engine Yard blog post on Getting Started with JRuby or the JRuby home site at jruby.org. You’ll find instructions on how to download, install, and get up and running with JRuby. If you’re interested in the project itself, check out JRuby’s kenai.com project page and wiki or our mirror repository on GitHub. And of course you’ll want to connect with the rest of the JRuby community, by joining our mailing lists, hopping on the #jruby IRC channel, or following us and @engineyard on Twitter.
What can I do to help?
There’s a lot of work to do in the JRuby project, and we certainly can’t do it all ourselves. So here are a few tips for folks interested in helping Ruby succeed on the Java platform:
- Try using JRuby! The more folks that use JRuby, the more feedback we’ll get and the better we’ll be able to make it. If you can’t use JRuby, then at least check it out and let us know what we’re missing. User feedback is taken very seriously by the JRuby team.
- Join the JRuby mailing lists and IRC channels, and help us support the JRuby community and the new Rubyists we’re bringing in.
- Submit bug reports for bugs you find, feature requests for features you think are missing, wiki updates and articles for topics you think need better coverage, and blog, blog, blog about your experiences. We need to work together to improve JRuby and get the word out.
- If you’re hacker-minded, check out JRuby’s source and see if you can help us fix a bug, add a feature, or improve performance. JRuby is a product of many, many external contributions, and would not exist today without community help. You can be part of the team too.
- Study alternative solutions to the problems Ruby and Rails solve so well, and let us know what you want out of JRuby. What do you need to make JRuby your web platform of choice? What are we missing compared to the alternatives? What would your perfect JRuby cloud or support offering look like? Don’t hold back…we’re eager to meet your challenges.
And finally, we would like to bid a fond farewell to our friends and colleagues at Sun Microsystems. We’re really going to miss you guys, and hope we can continue to work together on improving the JVM as a language platform. Thanks for everything.
Loading ...
Watch a Live Demo of Engine Yard AppCloud
The Engine Yard Newsletter
[...] Update: Charles Nutter posts about the move on the Engine Yard blog. [...]
[...] Charles, Nick, and Tom joining EngineYard to continue the development of JRuby. See Charle’s Post on EY’s blog and also his Comments at [...]
I've translate this in Japanese.
http://blog.chaaasan.com/archives/51232628.html
Congrats. Best of luck with the transition.
Correct me if I'm wrong, but 3 staffies on JRuby compared to 2 on Rails?
That's a pretty big commitment to JRuby.
Thanks for the JRuby pointers too, will take a look.
Interesting move. From the standpoint of enterprise acceptance, JRuby was easier to sell when you were still with Sun. "Honestly, Mr. Procurer, this software is created and supported by the people that built Java in the first place. It'll run on your IT architecture without adjustment or training."
I personally believe that enterprise acceptance starts with developers, and developers no longer trust the big, lumbering corporations like they used to. The JVM is the Platform of the People, and Ruby is the people-oriented language. Together they make a perfect combination, and what better company to shepherd the next round of JRuby evolution than Engine Yard?
In my experience the barrier to enterprise acceptance lies with purchasing divisions. Developers can be hyped up about technology, but if you or some champion don't manage to sway purchasers then it'll never make it into enterprise production.
That may be the case, but the purchaser doesn't simply throw a dart at a board. They measure reliability, supportability, TCO, ROI, TTM. Rails covers a number of those, and a commercially-backed JRuby can cover most of the others. And I think we've shown that JRuby is a strong, viable technology made stronger by the backing of a world-class Ruby and Rails company.
However, I'd love to talk with you offline about your theories on adoption. I'm sure we could learn from you and you may be able to learn from us. Our goal is to make JRuby the best JVM language and runtime we can possibly make it, and we'll leave no stone unturned along that path. Feel free to email me directly.
I should also mention that we have the deepest respect for Sun and loved working with them. They helped teach us the value of the developer, and helped us realize that technology decisions are made (and should be made) from the bottom up. We look forward to continuing to make JRuby the "developer's best friend", just like Ruby is a language designed "for programmers."
I should also mention that we have the deepest respect for Sun and loved working with them. They helped teach us the value of the developer, and helped us realize that technology decisions are made (and should be made) from the bottom up. We look forward to continuing to make JRuby the "developer's best friend", just like Ruby is a language "optimized for programmers happiness."
I'm curious about the difficulties while working at Sun…
Congrad for the new move!
Thanks Koz! We're really glad the team is on board!
[...] what is definitely the “coup of the week,” the JRuby team has decided to move wholesale from Sun to Engine Yard. Engine Yard has done an outstanding job at concentrating major amounts of Ruby experts in one [...]
What about Android support? Mr. Ruboto?
http://blog.headius.com/2009/02/ruboto-is-your-fr...
Any planned work on that beyond the initial accomplishments from earlier this year?
Domo Arigato, Luigi!
First off, you should check out my blog post from this weekend:
http://blog.headius.com/2009/08/return-of-ruboto….
Ruboto (JRuby for Android) lives! And we're not the only ones that think JRuby on Android is an awesome idea…the Android Scripting Environment now supports JRuby too:
http://amazing-development.com/archives/2009/08/0...
We (The JRuby Team) plan to also make JRuby usable as an *application* language for Android, with all the capabilities (and hopefully equivalent performance) as Java-based apps. We also received many comments from people trying out JRuby on Android this weekend, and several of them are interested in working with the JRuby team to build it into a first-class runtime for the Android platform. So rest assured, JRuby on Android is moving forward very quickly now.
How does this impact Rubinius? Hoping that EY continues to fund Rubinius development.
Hi Phred,
Engine Yard is indeed continuing to fund Rubinius development. The two full time developers on the project, Evan Phoenix and Brian Ford, are still very much at work and making progress :)
[...] have Java EE 6 support and recent GlassFish v3 as the default (Milestone 1 is just out). • JRuby guys moving to EngineYard (and confirming the GlassFish praises). • GlassFish v2.1 patch 3, for paying customers. • [...]
[...] So, after a long, busy summer, I’m finally back onto support of the various bits for JRuby web application development (meaning Warbler and JRuby-Rack). I’m pleased to announce the 0.9.5 release of JRuby-Rack and the 0.9.14 release of Warbler! All of this brought to you courtesy of Engine Yard, my new employer! [...]
Hi Charles,
We which you good luck with JRuby at your new home.
Regarding the support for REST in JRuby, I suggest that you have a look at our Restlet Framework (http://www.restlet.org) which has support for JAX-RS in addition to its more powerful Restlet API and is available in several editions: JSE, JEE, GAE, GWT and Android.
We would be happy to support you in this effort.
Best regards,
Jerome Louvel
–
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com