“The TypeScript compiler solely finds minor errors”
Uhm, sure. Precisely proper.
“All these sorts 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 might make it to deployment if not caught by way of testing. It’s all the time higher to seek out an issue earlier within the growth cycle, and nothing is sooner than slightly purple squiggly displaying up instantly as you kind an error.
As for “Too many errors,” nicely, that’s a characteristic. 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 manner too many “Guess what this JavaScript code would output!” issues. If there’s 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 must be, you will have dangerous code.
“I can use unit testing to verify my code works correctly”
That is one argument that offers me pause. I like unit testing and test-driven growth, and I believe all of us must be writing our code that manner, so this argument is compelling. However then I do not forget that you are able to do unit testing with TypeScript as nicely, so this argument sort of falls aside.
