Why Become a TypeScript Fan?
I am empathetic to many of the reasons that folks enjoy using static types in JS, and there are many pros to using TS, but I don&#x27;t find the arguments here to be persuasive at all. And as an engineering manager, I find some of these to be concerning.<p>Point #1 might be the strongest point, but it also assumes that your entire dependency graph is also type-safe, which is rare currently in the JS world (though that seems to be trending upwards).<p>Point #2 suggests that the class of bugs that were caught on the front-end could only otherwise be caught at compile-time by TS. In this example, its really just a question of whether you want syntax&#x2F;semantics in your code to prevent these bugs or unit tests to assert correct application behavior. You could easily make the argument that the former is more expedient, I buy that. But it&#x27;s not some exclusive domain of value in favor of TS. Arguably you could be using both approaches, but I find that increased surface area of unit tests (to cover the type error burden) is de minimis in the big picture.<p>Point #3 is similarly concerning. I hear this a lot from newer devs, that they can breathe a sigh of relief in thinking they can go make a ton of refactoring changes to their app and know that TS will prevent them from making egregious errors. But in fact, you can easily refactor an entire application and the output can be both type-safe _and_ have the behavior changed such that it no longer meets acceptance criteria.<p>On balance, if we had native type annotations in JS I&#x27;d use them, but I haven&#x27;t really heard convincing value arguments (yet) to just go all-in with TS.