[respondo2134]

>> Firstly, the simplest problem to fix with typescript would be to remove the "any" type, with that in the language, it lets lazy developers be lazy and negates the fact that you have typing in the first place.

I remember when TypeScript was first introduced. 'any' is what allowed it to become the player it is today, because you could use the entire JS ecosystem with very little rework. If you'd of had to redevelop everything up the stack to primitive types it never would have gotten traction.

How is this any different from strongly typed languages that ultimately resolve to 'object'?

Your arguments sound a lot like letting better be the enemy of perfect. TS doesn't have to have runtime type checking (I'd argue it should not) to be a huge productivity gain.

[wexomania]

In that sense I guess you are right, One could also argue that it is possible to write JavaScript in such a way that gives some of the same benefits as TypeScript, but that requires more discipline, and it probably scales badly with larger teams.

I guess i might just have to go on the same journey as OP...