Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
If MRI is a potato peeler that does one thing very well, JRUby is the Swiss Army Knife that offers developers a multitude of tools. JRuby opens doors that MRI has closed, being highly performant and offers access to Java libraries. From the perspective of a former MRI'er, I'll discuss concrete examples of how to realize the benefits of the JRuby stack, drawing examples from my work on an open-source JRuby on Rails app. Help us caption & translate this video! http://amara.org/v/FGc0/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the presentation titled "Why I like JRuby (and you should too)" at LA RubyConf 2013, Fiona Tay, a Ruby and JavaScript developer, explores the benefits of using JRuby, a Ruby implementation on the Java Virtual Machine (JVM). While the title suggests a personal preference for JRuby, the talk centers around when to choose Ruby versus JRuby based on application requirements. **Key Points Discussed:** - **Introduction to JRuby:** JRuby allows developers to run Ruby applications on the JVM, making it a practical option in enterprise environments that commonly use Java. - **Compatibility and Setup:** Transitioning a project from MRI (Matz's Ruby Implementation) to JRuby is straightforward, mainly requiring the installation of JRuby and adjusting configurations, especially if using RVM (Ruby Version Manager). - **Performance and Libraries:** - JRuby provides access to a wealth of Java libraries, such as the Stanford Parser for Natural Language Processing and JavaMail for advanced email functionalities. - Deployments with JRuby can utilize Java infrastructure, such as packaging Ruby applications into WAR (Web Application Archive) files for easier deployment on traditional Java environments. - **Concurrency Benefits:** Unlike MRI, JRuby supports true multithreading, allowing for better concurrency, which enhances performance in web servers and can reduce the need for additional hardware. - **Caveats of JRuby:** - Certain gems, especially those with C extensions, may not be compatible with JRuby, affecting functionality. - With test-driven development in larger Rails projects, developers might experience longer startup times with JRuby, which could impact productivity. - JRuby, while mature, is not as widely adopted as MRI, leading to potential compatibility issues with libraries primarily developed for MRI. **Examples and Case Studies:** - Fiona references Open Chorus, an open-source project with significant testing that benefits from using JRuby. - She notes Twitter's initial use of MRI before transitioning to JRuby to cope with scalability challenges. **Conclusion and Takeaways:** - The choice between JRuby and MRI should depend on your application's specific needs. JRuby is advantageous for projects that can utilize Java libraries, require high performance, or are operating in Java-centric deployment environments. Conversely, simpler applications may not need the complexity of JRuby.
Suggest modifications
Cancel
