Q&A with Yukihiro Matsumoto (Matz)
summary
Adds concrete changes and limits: pattern matching lands as an experimental, slower but expressive feature; core plans copy the async gem internals to give true I/O‑multiplexed async APIs for sockets, files and DB access; pipeline and dot‑colon operators get tried then retracted after community confusion; small legacy features face staged deprecation with warnings before removal; MRI stays separate from mRuby; Ruby 3.0 aims for next year barring disasters.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:26Looking Back at Ruby's History
- 13:31Future To Add Pattern Matching
- 18:06Would You Encourage Others To Play with Making Their Own Programming Languages like You Did with Ruby
- 34:40What Is an Upcoming Change or Addition to Ruby that You Are Personally Most Excited about
- 34:51Pattern Matching








