This version of Vestibule is read only. It represents an archive of the community effort to produce content for Ruby Manor 4.

Cranking it up with JRuby and TorqueBox

updated over 7 years ago; latest suggestion over 7 years ago

This proposal has been withdrawn...

Every Rubyist likes to hate on Java.

But JRuby is now fast and robust and tools like TorqueBox bring enterprise deployment to the Ruby community.



  • Acd62030df551952268e84c8fff26a5b James Adam suggests over 7 years ago

    Also, what is "enterprise deployment"? Do you mean using Ruby in situations where the JVM is mandated? Or the actual act of deploying code onto servers in a more "enterprise" way (and if so, what does that mean)?

    Please don't take any of these points as criticism - I'm very curious to see you expand this into a more detailed proposal :)

  • F6f41097bd9390607fe4f1e7288c72e3 Tom Armitage suggests over 7 years ago

    "tools like Torquebox" - such as? Whilst focusing on a single tool might be best for a focused talk, it'd be useful to know where Torquebox sits in the ecosystem; does it have alternatives? Why is it better or worse?

    Personally, at RubyManor, I'd like to see something a notch deeper than "here is a thing!". So a talk about JRuby platforms in 2013, with emphasis on Torquebox, feels more appropriate than a talk about a single product with a slide about alternatives/competitors.

    I guess I want more detail than "boom".

  • Acd62030df551952268e84c8fff26a5b James Adam suggests over 7 years ago

    I can feel your enthusiasm, but I think a bit more detail is required :)

    For example: what aspects of TorqueBox are you going to cover? Do you expect to need to talk about JRuby?