I don't think you understood the blog post (which is presumably my failure as an author; it was just an off the cuff post and I didn't edit it especially carefu

I don't think you understood the blog post (which is presumably my failure as an author; it was just an off the cuff post and I didn't edit it especially carefully). The point is not to compare JS and C (interesting though that would be) but to note ways in which both of them may be slowly superseded by languages which target the same environments they do but allow much more developer confidence along certain axes—and, in my experience, therefore also a better developer experience and higher productivity along those axes. The whole point was that Rust, Elm, etc. can and do prevent whole classes of problems that are difficult (at best) to eliminate when writing C or JS respectively—Rust and Elm (and F and OCaml and Haskell and Idris and…) were essential to the point I was getting at. One of the challenges for dealing with hype is that things which are legitimately really good tend to get hype, but things which get hype aren't necessarily good. In my experience, Rust is actually really good (so much so that I ran a podcast about it for a couple years). So are lots of other things. It's not perfect, by a long shot. But while there's some of the people hyping it because it's cool phenomenon—that's real!—people also get excited by finding a tool they really enjoy, that solves real problems they experienced previously.