“The TypeScript compiler solely finds minor errors”
Mmm, sure. Precisely appropriate.
“All these guys create too many errors”
Mmm, sure. Precisely appropriate.
Properly, these final two feedback have been just a little flippant. However the errors are the purpose. The TypeScript compiler will discover errors that would make it to the implementation if not caught by testing. It is all the time higher to seek out an issue earlier within the improvement cycle, and nothing occurs before just a little crimson squiggle that seems instantly while you kind a bug.
As for “Too Many Bugs”, nicely, that is a characteristic. TypeScript is exact and precision is nice and fascinating when coding. There isn’t any restrict to the methods you may shoot your self within the foot with JavaScript. I see too many “Guess what this JavaScript code would produce!” points. 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 your consequence needs to be, you might have dangerous code.
“I can use unit checks to verify my code works appropriately”
That is an argument that makes me suppose. I like unit testing and test-driven improvement, and I believe we must always all write our code that means, so this argument is compelling. However then I bear in mind which you could additionally unit take a look at with TypeScript, so this argument falls aside.
