News for hackers. Stuff that matters.

A comment on Go: What We Got Right, What We Got Wrong. Parent comment

Re:Go: What We Got Right, What We Got Wrong by worik on Friday January 05, 2024 @03:38PM (#38884563)
> ...finding enormous success as a statically typed (and an order of magnitude faster) alternative to Python.

An alternative to Node.js/{Java|Type}Script catastrophe

I have not written any go but I have been dragged into Node.js programming, and it is awful

I do not believe in rewriting systems (except in exceptional circumstances that do not apply) so I'm stuck. But for someone else's choice...

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by rreichman on Friday January 05, 2024 @03:53PM (#38884786)
Interesting that you say Node programming is a catastrophe, I think it’s fantastic.
[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by worik on Saturday January 06, 2024 @04:30PM (#38895683)
I have used Node a lot.

And many other systems over the decades.

Node is catastrophic because it perpetuates mistakes make fifty years ago where other modern systems (looking at Go and Rust) learnt from the past mistakes not to repeat them

If Node were not popular it would not be catastrophic

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by matheusmoreira on Monday January 08, 2024 @11:20AM (#38914228)
Which mistakes?
[ Parent | on HN ]