upvote

points

by userbinator18 hours ago |
comments
upvoteby jazzypants8 hours ago|
next
[-]
Literally nothing has degraded. What in the world are you talking about? All of this stuff is optional.
reply
upvoteby michaelchisari18 hours ago|
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."

reply
upvoteby halapro15 hours ago|
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.

reply
upvoteby saghm14 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
reply
upvoteby Maxion15 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.
reply
upvoteby albedoa2 hours ago|
parent|
prev|
next
[-]
The guy you are responding to is longing for what was possible two decades ago. He is that one idiot. He even replied to your comment with confirmation!
reply
upvoteby userbinator15 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".
reply
upvoteby josephg10 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.

reply
upvoteby userbinator2 hours ago|
parent|
[-]
"support" and "works" are two different things.
reply
upvoteby Griffinsauce14 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. .
reply
upvoteby userbinator2 hours ago|
parent|
[-]
That's also a problem. I've written JS that would work on any browser from the latest ones all the way back to IE5, and I'm not even a professional JS developer. It's not hard.

Maybe "professional" is the problem: they're incentivised to make work for themselves so they deliberately add this fragility and complexity, and ignore the fact that there's no need to change.

reply
upvoteby 14 hours ago|
parent|
prev|
[-]
deleted
reply
upvoteby prinny_11 hours ago|
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.
reply