The newer version is often even more bloated. This whole article just reinforces my opinion of "WTF is wrong with JS developers" in general: a lot of mostly mindless trendchasing and reinventing wheels by making them square. Meanwhile, I look back at what was possible 2 decades ago with very little JS and see just how far things have degraded.

▲

jazzypants 2 hours ago | parent | next [-]

Literally nothing has degraded. What in the world are you talking about? All of this stuff is optional.

▲

michaelchisari 11 hours ago | parent | prev | next [-]

A standard library can help, but js culture is not built in a way that lends to it the way a language like Go is.

It would take a well-respected org pushing a standard library that has clear benefits over "package shopping."

▲

halapro 9 hours ago | parent | prev | next [-]

> WTF is wrong with JS developers

Don't confuse "one idiot who wants to support Node 0.4 in 2026" with "JS developers". Everybody hates this guy and he puts his hands into the most popular packages, introducing his junk dependencies everywhere.

▲

saghm 8 hours ago | parent | next [-]

If everyone hates him and thinks his dependencies are junk, why would anyone let him introduce them to popular packages? Clearly there are at least some people who are indifferent enough if the dependencies are getting added elsewhere

▲

Maxion 8 hours ago | parent | prev | next [-]

The other problem is that this is a bit of a circular path, with deps being so crap and numerous, upgrading existing old projects become a pain. There are A LOT of old projects out there that haven't been updated simply because the burden to do so is so high.

▲

userbinator 8 hours ago | parent | prev [-]

Then I wish there were more of these "idiots who want to support Node 0.4 in 2026". Maybe they're the ones with the common sense to value stability and backwards compatibility over constantly trendchasing the new and shiny and wanting to break what was previously working in the misguided name of "progress".

	▲	josephg 4 hours ago \| parent \| next [-]
		NodeJS has a clear support schedule for releases. Once a version of nodejs is EOL, the node team stops backporting security fixes. And you should really stop using it. Here's the calendar: https://nodejs.org/en/about/previous-releases Here's a list of known security vulnerabilities affecting old versions of nodejs: https://nodejs.org/en/about/eol In my opinion, npm packages should only support maintained versions of nodejs. If you want to run an ancient, unsupported version of nodejs with security vulnerabilities, you're on your own.
	▲	Griffinsauce 8 hours ago \| parent \| prev \| next [-]
		You wouldn't if you look more deeply at this. He doesn't push for simplicity but for horrible complexity with an enormous stack of polyfills, ignoring language features that would greatly reduce all that bloat. .
	▲	7 hours ago \| parent \| prev [-]
		[deleted]

▲

prinny_ 5 hours ago | parent | prev [-]

I believe if you read this article https://www.artmann.co/articles/30-years-of-br-tags your "wtf is wrong with js developers" question will be answered.