Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
NodeJS is an accumulation of wrongs justified by a good compiler.
@TheWrongGod Honestly, yes.
The whole ecosystem is in my opinion an architectural fail.
Starting from proper versioning, to the organisational problems (look up the history behind the NodeJS forks)… the security problems, the lack of accepting critic, the lack of integration - up to the point of actively excluding - foreign projects like Yarn ...
I could go on.
But really, if you study the history of NodeJS, there are too many dark spots imho.
The really worst is that even the successors like deno didn't learn from these mistakes.
I.e. dreno has no package management, explicitly allowing any form of package management.
I wish I could say that this is just the tip of the iceberg, but when you look at the development of a lot of JS projects, you see the same behaviour.
"We didn't like X and Y, so we invented Z. Z has the same problems as X, with the syntax of Y."
Yay. G r e a t.
@TheWrongGod That's the wrong question in my opinion.
Just find out what you like.
My hatred for JS - I deny any project requiring or running JS - is based on facts, but it's still an opinion.
Every language has it's cons and pros, but in my opinion JS is a tumorous cancer that feeds on itself.
Try DotNet, if you like it, stick with it.
Anything else than JS. If you want money, go for cobol - myriads of migration projects await ya.