No, we haven’t forgotten how to code.
So there was this (admittedly) annoying hickup — for a few hours some critical dependency was down and inevitably we’re getting flooded with the ‘serious talk’ as in “JS is broken”, “JS is the new Java”, “Ha! That’s why I moved on to Golang”, “Kids can’t code anymore”, etc.
And inevitably, 99.5% of it is missing the point.
Over that the last decade or so every aspiring programmer on the planet has gotten DRY hammered into their brains a thousand times over (not that it was a particularly innovative concept even back in the days when a certain Ruby framework was all the rage). Dependencies have always been a part of economical coding. It’s a simple a tradeoff between “getting things done” vs “getting bogged down by a buttload of buggy, poorly crafted, poorly tested DIY code”
Telling people that they now should return to writing everything from scratch or switch boats altogether (just to run into similar problems & discussions a year down the road) isn’t going to fix anything.
JS and it’s ecosystem might have it’s shortcomings as has any other language but it’s still an efficient tool to solve a large set of problems and it’s a lot less of a dependency mess than others (Looking at you, PHP & Ruby). It’s easy to learn and it runs almost everywhere.
JS is here to stay. Dependencies are to stay. Get over it.
The only meaningful discussion to be had is how to better deal with them — Why npm should even allow to un-publish packages? How to reconcile brand and community interests? (npm has namespaces now) Could we provide a properly maintained “standard library” for trivial tasks? (like jshttp does for http)