Programming language evolution: with all that, we are still flying
zverok.github.io · 2,403 words · saved by 1 readers
Final part of adventures in understanding, explaining, and challenging the facts that should be obvious. (Part 1 → Part 2 → Part 3)
Final part of adventures in understanding, explaining, and challenging the facts that should be obvious. ( Part 1 → Part 2 → Part 3 ) This article is written for my Substack , you can subscribe to it by email now! In the previous two parts, I described how working on Ruby’s changelog made me imagine I understand language’s logic and intentions behind it. Then, that fantasy brought me to participate more insistently in language development. And then, that participation made me suffer when several aspects of Ruby 2.7 evolution hasn’t developed the way I expected—and in one case, an important fea
saved by
related reading
- combinators in Rubymooreniemi.github.io
- Things unlearnedscattered-thoughts.net
- how I think when I think about programming - alice mazalicemaz.com
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- Leaving Haskell behind - Infinite Negative Utilityjournal.infinitenegativeutility.com
- Software development topics I've changed my mind on after 10 years in the industrychriskiehl.com
- Reflections on a decade of codingscattered-thoughts.net
- Introduction · Crafting Interpreterscraftinginterpreters.com
- A break from programming languageslexi-lambda.github.io
- The Alternative Implementation Problempointersgonewild.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- The Curse of Knowing How, or; Fixing Everything | Blognotashelf.dev