“The TypeScript compiler solely finds minor errors”
Uhm, sure. Precisely proper.
“All these varieties create too many errors”
Uhm, sure. Precisely proper.
Okay, these final two feedback have been a bit flippant. However the errors are the purpose. The TypeScript compiler will discover errors that would make it to deployment if not caught by way of testing. It’s all the time higher to search out an issue earlier within the improvement cycle, and nothing is sooner than a bit purple squiggly exhibiting up instantly as you sort an error.
As for “Too many errors,” properly, that’s a function. TypeScript is exact, and precision is nice and fascinating when coding. There’s no restrict to the methods you’ll be able to shoot your self within the foot with JavaScript. I see approach too many “Guess what this JavaScript code would output!” issues. If there may be ambiguity and imprecision in a language, that language will lead to buggy code. If it’s a must to run code to know what its output needs to be, you’ve unhealthy code.
“I can use unit testing to ensure my code works correctly”
That is one argument that offers me pause. I really like unit testing and test-driven improvement, and I feel all of us must be writing our code that approach, so this argument is compelling. However then I keep in mind that you are able to do unit testing with TypeScript as properly, so this argument type of falls aside.
