Side note, but this article reads like a Wes Anderson film, if that makes any sense.

While I am totally on board with the idea... the article doesn't really say what to actually do to help?

"we at Handmade community" - and no link to that community anywhere

blog itself? 2 posts a year, and 2025 posts aren't even on the blog itself (just redirects)

Yes, tooling and toolmaking should be promoted - but promotion itself should also be accessible somehow?

This is a good reminder that abstractions are supposed to help us solve problems rather than just hide the details. I feel like I spend too much time fighting against tools that try to prevent me from seeing how things really work.

While directionally correct, the article spends a lot of time glorifying jquery and not enough on what a horrible, no good, unoptimized mess of a framework jquery was, and by extension what kinds of websites were built back then. I remember those times well. The reason to use React isn't because it was new, far from it. It was because it won vs. Ember, Angular, et. al. in 2014-2015? as the best abstraction because it was easiest to reason about. It still wasn't great. In fact, still isn't great. But it's the best blend of many leaky abstractions we use to code against the browser apis.

I enjoyed reading this article but I think the author overlooked that "low-level" languages aren't just less supported, they're also character-dense. You can accomplish more with less, simply because it's a higher level abstraction. If you choose to abstract through this problem, aren't you creating a high-level language?