The Ruby Implementors panel
summary
Panelists compare concrete implementations: JRuby runs Ruby on the JVM to reuse Java libraries but hurts startup time; RubyMotion forks MacRuby to ship iOS apps and removes proc binding to gain speed; Rubinius pursues a bytecode VM and Ruby-in-Ruby for easier hacking; MRI gains a generational GC and frozen-string optimizations yet suffers from a C-API that blocks portable native extensions and legacy features like taint slowly disappear.
AI-written summary · about
chapters (17)
- 0:00Ruby implementors panel intro
- 4:01Why new Ruby implementations
- 8:57RubyCocoa with Objective-C
- 16:42Ruby's market relevance
- 25:48Hip versus relevant in Ruby
- 32:04Ruby 2.1 frozen strings
- 40:58Ruby design trapdoors
- 46:14Stump the implementer
- 52:34Ruby GC challenges
- 55:00Software transactional memory in Ruby
- 1:00:36Ruby encoding edge cases
- 1:03:02Wow moments in Ruby
- 1:04:49What each implementation wishes it did better
- 1:10:49Unsolved Ruby problems
- 1:15:24Ruby C API limits
- 1:17:49Fast Ruby code tips
- 1:22:03Closing remarks
