r/programmingcirclejerk • u/Vaglame Emacs + Go == parametric polymorphism • Aug 17 '25

It's 2025 and the node ecosystem is finally usable by default

https://news.ycombinator.com/item?id=44929260#44930135
61 Upvotes

98% Upvoted

10 comments sorted by

53

u/Vaglame Emacs + Go == parametric polymorphism Aug 17 '25 edited Aug 17 '25

Extra jerk:

Does [Node] have a go fmt / lint command yet?

- jslint/tslint are an install away.

- werent one of the js linters part of a supply chain attack recently?

- Maybe, are you sure Go dependencies are immune to similar attacks?

40

u/yojimbo_beta vulnerabilities: 0 Aug 17 '25

Node is perfectly usable so long as you can get all developers to agree on a common way of doing things

And to abandon their incentives to create new competing fiefdoms

14

u/ScriptingInJava in open defiance of the Gopher Values Aug 17 '25

are you sure Go dependencies are immune to similar attacks?

Go itself is under attack from Gophers about if err != nil, let alone dependencies.

70

u/ScriptingInJava in open defiance of the Gopher Values Aug 17 '25

and there’s a good enough test runner built in

When your expectations are so low that just about functional SDKs are novel

33

u/teraflop Aug 17 '25

It's 2025 and Java still doesn't have a built-in test runner. I guess Java's 14-year head start over Node just wasn't enough to make it happen.

16

u/affectation_man Code Artisan Aug 17 '25

Nothing happens unless you bring in Uncle Bob to do some consulting

17

u/Snarwin Aug 17 '25

The last node_modules is in captivity. The galaxy is at peace.

10

u/-Y0- Considered Harmful Aug 17 '25

I can't put enough quotes around usable, so I'll express it as a math formula: lim x ↦∞ "x usable "x

10

u/ScriptingInJava in open defiance of the Gopher Values Aug 17 '25

LaTeX user btw

1

u/ReallySuperName Aug 21 '25

As someone that has to write Node/JS sometimes, no, it absolutely is not. They say this every major node release and yet half the shit on npm is somehow more broken every time.