I've done back ends in TypeScript/Node. The TypeScript part is great; the rest is still Node and has awful, frustrating downsides. Package management remains a disaster.
I haven't tried them yet, but Rust and Kotlin are next on my list. I really can't stand working without static typing anymore.
Same here, I've worked on projects without static typing and it's more painful without the safety of the compiler. Rust is also on my list.
I do think that programming in Python got me comfortable with passing functions around and a few things that were easier in dynamic languages so I'm always glad about that.
You use TypeScript instead of JS for Node? Interesting...
"You use TypeScript instead of JS for Node? Interesting..."
I'm actually flabbergasted that anyone can write a large, complex Node back-end without TypeScript. Even with fantastic IDE support from WebStorm, jslint/hint, and great discipline, there is just way too much ambiguity, doc-reading, and simple mistakes.
Comments
I've done back ends in TypeScript/Node. The TypeScript part is great; the rest is still Node and has awful, frustrating downsides. Package management remains a disaster.
I haven't tried them yet, but Rust and Kotlin are next on my list. I really can't stand working without static typing anymore.
Same here, I've worked on projects without static typing and it's more painful without the safety of the compiler. Rust is also on my list.
I do think that programming in Python got me comfortable with passing functions around and a few things that were easier in dynamic languages so I'm always glad about that.
You use TypeScript instead of JS for Node? Interesting...
I'm actually flabbergasted that anyone can write a large, complex Node back-end without TypeScript. Even with fantastic IDE support from WebStorm, jslint/hint, and great discipline, there is just way too much ambiguity, doc-reading, and simple mistakes.
Say what now? You’re saying npm is a disaster? That is surprising.