“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 had 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 at all times 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 kind 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 means too many “Guess what this JavaScript code would output!” issues. If there’s ambiguity and imprecision in a language, that language will end in buggy code. If you must run code to know what its output must be, you have got unhealthy code.
“I can use unit testing to ensure my code works correctly”
That is one argument that provides me pause. I really like unit testing and test-driven improvement, and I believe all of us should be writing our code that means, so this argument is compelling. However then I do not forget that you are able to do unit testing with TypeScript as properly, so this argument sort of falls aside.
