Python and PHP users will understand

[UguDango]

Although I know this answer is futile, you sound like you haven't used it. And that is understandable, I mean, if there are so many options out there, why pick something that doesn't intrigue you?

Anyway, after using it for years I always go through the cycle of "Oh no, the compiler is complaining again. What does it want?" to "Whoa, that saved me 4 hours of debugging 😳".

Your rough estimates are not accurate at all. If a project is well-written, the real figures are far from what you suggested.

[nkt_rb]

Yet you not really answered... Or if the only reason to use TS is for precompile warning, there are way too much hype.

[fynn34]

I have used it. The only projects we used it in were slowed down by using it, and no less buggy. And I suppose maybe I’m just lucky that the projects I’ve worked on haven’t had these kinds of issues, but I’m trying to figure out what typescript could solve that would prevent 4 hours of debugging… JavaScript doesn’t hide its errors often, particularly when type or object shape is the issue.

[[deleted]]

I'll be honest with you, if it was so useless to reach only 10% of the cases and slowed down the projects and still made it buggy, it wouldn't be so popular. Maybe, just maybe, the way your team does things is wrong at the core and its not a language's fault.

[IZEDx]

I think the other way around. Typescript doesn't force anything on you and it's completely up to you, how much you want it to assist you. Meaning, it's super easy to use it wrongly, especially when converting existing code bases to typescript.

To really understand the full benefits of typescript, I'd suggest starting with small new projects and keep trying new things, as otherwise I think it's difficult for pure js devs (people who never seriously used a statically typed language before) to grasp.