Language as a Tool of Thought: Consistency versus Progress
summary
Argues that the language people use shapes how they think and shows which Ruby changes actually move that needle: concrete feature work on method references (recent operator reversal), enumerator chain and endless/beginningless ranges, and the limited impact of numbered parameters as mere sugar. Notes many proposals get accepted or rejected, maintains the Ruby changelog, and points to how these specific additions or reverts change code flow, composability, and how easy it is to build larger systems.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:16Is programming language a tool of thought?
- 5:11Properties of a good material
- 11:34Chaining and code flow
- 13:30Everything is an object. But what does it mean?
- 18:06Secondary reasons
- 22:26Language evolution is
- 23:05Empower individual objects
- 28:32Atomics in the flow: Method references
- 32:25Frequent first reaction to change
related talks
26mhow a language affects its people
36mTowards a Higher-Level Language
47mA Game of Theories: why languages do what they do
33mRuby: A Family History
36mRuby's Creed
34mThe Modern Rubyist: When and How to Use the Latest Features
45mHow Programming in Other Languages Made my Ruby Code Better
27mThe state of Ruby dev tooling