Ruby's Creed
summary
Argues that Ruby’s creed — optimizing for programmer happiness — is real but vague, and evaluates concrete changes: Ruby 3 lands after ~5,000+ commits per release, pattern matching and keyword-argument separation evolve, Set becomes builtin so requiring it disappears, data class fixes Struct quirks, anonymous block-arg and argument forwarding spark controversy, fibers and fiber storage ship, and RuboCop embeds native LSP support in rubocop to run a faster LSP server. Claims tradeoffs between stability and new features and that happiness is individual.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 3:52Rubocop LSP support
- 5:45Ruby’s philosophy
- 9:38Culture as behaviors we reward and punish
- 12:30Happiness in Ruby
- 16:47Programming preferences
- 19:41Grading Ruby releases
- 26:10Ruby’s evolving identity
- 28:18Ruby as Swiss Army knife
- 31:56Ruby community values
- 32:41Q&A
related talks
34mThe Modern Rubyist: When and How to Use the Latest Features
43mRuby: The Challenges Ahead
33mRuby: A Family History
41mDeconstructing a hype: What people think is wrong with Ruby?
35mRuby Makes My Brain Happy
49mDeconstructing the hype: What people think is wrong with Ruby?
01h 06mRuby3 challenges
47mKeynote: Beyond Ruby3.0