Really? You hate python but recommend typescript? All the problems you cited about python are there, too!

Garbage stack traces that go through a hundred lines of node modules.

Dependency hell. Peer deps. Npm or yarn? An ecosystem where packages have a half life of weeks. A new major version of node comes out literally every six months. SIX MONTHS. MAJOR VERSION CHANGE. And you complained about python2 vs 3!

Typescript also has a garbage debugger compared to python.

There’s also just too many ways of doing things because the standard lib is thin. How many ways to loop over an object are there? For in, for each, object keys, lodash, underscore, object.entries, what am I forgetting?

Newer versions have stuff in the standard lib like Array.at, but if you’re targeting an older browser that won’t work unless you enter the wonderful world of transpiling and polyfills. And you thought virtualenv was bad??

And let’s not forget the language’s obsession with being async, even when you don’t expect or want it. How many hours have been lost because someone forgot to await response.json()?

Oh right and remember how there’s like six ways of declaring a function. The function keyword, when it’s in a class, and like four variations on arrow function syntax. And arrow functions are different than ones with the function keyword.

And lots of other little weird gotchas like

const foo = "hello";
const bar = { foo: "world"};

Go on. What do you think that object key is? The syntax is insane . You need to do { [foo]: “world”} to reference a variable as a key. Which looks like a list. Because typescript/javascript is kind of bad.

Typescript is used in the browser because that’s the only thing really supported there for front ends. It’s a horrible tool for anything else.