Panel Session with Ruby Core Team
summary
Monthly developer meetings in Tokyo and Redmine track decisions; contributors must submit a patch, add it to the meeting agenda, then wait for Matz to sign off. Core work uses trunk: people build Ruby daily and one team tested Ruby 2.5 in production but rolled it back for server consistency. Requests include first-class fork hooks for unicorn. Performance hope rests on Vlad’s JIT, while types stay experimental—there’s a private types-in-Ruby fork for static checks but it risks breaking duck typing.
AI-written summary · about
chapters (34)
- 0:00Intro
- 3:00I like easy programming languages
- 4:00What would you look for in a Ruby program
- 4:40Do you look for Ruby experience
- 5:45Who are you looking for
- 7:15Ruby libraries
- 8:20Why dont we use Ruby
- 9:30How has Ruby changed
- 10:10Who is the language designer
- 12:25Do you have a system for rejecting proposals
- 13:30Hows your day like
- 13:50What do you look at everyday
- 15:15What do you look at daily
- 17:45What are your plans for Ruby
- 19:10What do you do besides writing code
- 20:25What is one of Rubys strengths
- 21:00Ruby Tuesday
- 22:10Avoiding governance structure
- 22:45Release schedule
- 23:25Backward compatibility
- 25:00Craziest thing
- 28:50Favorite thing
- 31:05Why are we adding types
- 32:10Type inference
- 34:10Types
- 35:05Private Fork
- 37:50English
- 38:30Commercial work
- 39:00Language work
- 40:05Resources
- 40:50Rubys Virtual Machine
- 41:30MRuby
- 44:50Ruby vs Elixir
- 46:25Why Tender Love
