Why I like JRuby (and you should too)
summary
Advocates switching to JRUby for concrete gains not hype JRUby gives direct access to Java libraries so the Stanford NLP parser and JavaMail run as Ruby code an open source project Open Chorus uses over 10,000 tests and ships on the JVM using Warbler to create WAR deployables deployment admins accept it while developer tooling suffers because Spork doesn't work and app startup is slow JRUby delivers real threads and measurable cost savings at scale but costs appear around gem C extensions compatibility and occasional library bugs
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:07What JRuby is
- 2:51Installing JRuby
- 6:28Java libraries in Ruby
- 8:13Calling Java from Ruby
- 10:16Easier deployment
- 11:42JRuby performance
- 13:10Gem compatibility
- 15:40Productivity downsides
- 16:23Library support
- 17:05Concurrency advantages
- 19:55Thread safety issues
- 21:18When to use JRuby
- 23:07Getting started
