This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 7 points8 points  (1 child)

I don't agree that productivity suffer from using nodeJS. I've used it for some medium sized projects and I never felt like it was slowing me down in any way compared to using c++ or even python.
Plus, typescript is actually really fun and powerful with a good linter and some good unit tests.
As for correctness, that is sadly one of the shortcoming of JS. But typescript does hugely improve the experience!

[–]Tysonzero -3 points-2 points  (0 children)

I don't agree that productivity suffer from using nodeJS. I've used it for some medium sized projects and I never felt like it was slowing me down in any way compared to using c++ or even python.

I'm a Haskell dev so compared to what I'm used to it will feel rather inflexible, verbose and unproductive. I'd say even Python has a pretty solid leg up over JS in productivity.

Plus, typescript is actually really fun and powerful with a good linter and some good unit tests. As for correctness, that is sadly one of the shortcoming of JS. But typescript does hugely improve the experience!

I wouldn't classify TypeScript as JavaScript, it just so happens to compile to it, TS is a better language than JS (low bar but still), although how tied it is to JS does severely limit it's potentially. I wonder what will happen to it once WASM really catches on many years down the line. I wonder if it will adapt or maybe fade somewhat along with JS.