I begin to feel node js is more like a way of training normal developers to using JavaScript's lameness since it fucking sucks overall

NodeJS is an accumulation of wrongs justified by a good compiler.

@IntrusionCM just interpreter performance ?

@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.

Yay.

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.

@IntrusionCM I begin to wonder what the good choice is

Dotnet seems a tad limited oob

@IntrusionCM but c# is awesome

@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.

@IntrusionCM oh there is more to consider

Anything developed in c# properly is a slight undertaking

Interface options aren't good either

@IntrusionCM At this point, should we just move on to Gradle for package management?

@OzzyTheGiant Never worked with gradle, sorry.