[jstclair]

I've worked on a large typescript project for the past 6 months with 5 developers, and this type of superficial analysis doesn't track at all with our experience. Yes, TypeScript is a superset of Javascript - aimed at making large projects more maintainable. If, as this seems to saying, you're starting with the assumption that JavaScript is a terribly flawed language, TypeScript probably isn't going to make things magically better. But then, perhaps you should consider working in a different area of your application (or the industry), because JavaScript is what we've got to work with.

[pekk]

It's not a prejudicial "assumption" adopted ahead of experience that JavaScript is a terribly flawed language. It is something one sees by experience with JavaScript. Actually, the existence of all these transpilers makes no sense if JavaScript is already so wonderful as it is.

It seems excessively defensive to tell people who express a desire for better solutions to get out of the industry. If everybody accepts bad tools out of learned helplessness then there is no impetus to make things better.

[wvenable]

I came here to make a similar point, the author states:

"TypeScript is not the answer. Or perhaps it’s more accurate to say it is the answer to a different problem."

And I think that's a valid point. TypeScript is an answer to the problem of developing and maintaining a large body of JavaScript code. JavaScript alone is pretty good for small scripting tasks and TypeScript is similarly too much overhead for small tasks.

But TypeScript does nothing to fix the "JavaScript minefield" which is what the author thinks needs to be solved.