At RailsConf I had just given a thorough, yet humorous, overview of why everyone should run their production Ruby web applications on JRuby or Rubinius. I introduce into evidence exhibit A, the video replay of my 15 minute keynote.
My beloved friend Aaron “Tenderlove” Patterson then stood up to give his own keynote and publicly rejected all my good advice with, “Ignore what Dr Nic said, [don’t use Rubinius or JRuby]. I’m on the MRI core team, so I think you should use that instead.” (paraphrased)
Oh really, Aaron. This calls for a Ruby Platforms Virtual Brodown. I invite you all to join us for the webinar event. We’ve lined up a great panel of folks. Each awesome panelist will represent a different implementation: Ruby MRI, JRuby or Rubinius.
###Ruby Platforms Virtual Brodown
“Why should I attend? This sounds like it could get ugly…” some of you may be contemplating.
Rightfully so. We know you have other options. Your 50 minutes could, very well, be better allocated to earning DJ points on turntable.fm, replying to heaps of email, or pondering summer getaways whilst billing hours.
However, if you decide to join us, we’ll vow to leave you with a solid understanding of Ruby MRI, JRuby and Rubinius. More specifically, we will cover:
- The Ecosystem: What works where, integrations and other capabilities to know about
- Tooling: Profiling, debugging, monitoring, VPN introspection
- Concurrency: Threading models and doing two things simultaneously
- Windows: Life on planet Windows
- Deployment: Sample stacks and how to run in production
We hope this laundry list of takeaways is enough to convince you to register to attend, or at least register to watch the recorded version we’ll email you post-event.
Hope you can make it.