Where is Ruby Really Heading?
summary
A concrete checklist: porting prawn from Ruby 1.9 back to 1.8 costs about 80–90% of the initial effort unless compatibility is designed in; Ruby 1.9 requires magic file-encoding comments and explicit binary IO to avoid subtle bugs; create automated examples plus unit tests and run them under a branch until green; use ZenTest or multi-version loops to catch regressions; wrapping C APIs via ffi (about 60 functions in one project) proves cross-platform and works immediately, JRuby often simplifies Windows integration.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:29Prawn project choices
- 9:49Ruby 1.9 encoding
- 17:56Backporting 1.9 features
- 25:29Ruby 1.8.7 transition
- 32:13Cross-platform with FFI
- 37:14Ruby implementations
- 44:40Ruby Spec future
- 45:44Q&A
