2 ms·
If you follow the link in that reference, you'll see that the claim that TypeScript does not reduce bugs much is backed up by 4 independent sources.
by ericelliott 7y ago
If you follow the link in that reference, you'll see that the claim that TypeScript does not reduce bugs much is backed up by 4 independent sources.
- vikingcaffiene 7y agoMy claim comes from having built large scale systems with and without TS. I have the scars from working without it and I'll never do it again if I can help it. I'll also say that it's possible to write bad buggy code no matter what tooling you use. It's a "pit of success" thing for me. I want to at least make sure the super dumb stuff doesn't make it through. IMO you should use all the TDD, documentation, and code/design review in ADDITION to a type system.
- ericelliott 7y agoYeah. I've done that, too, and TypeScript certainly can catch up to 20% of the public bugs on GitHub. But I find that after all the other measures I use (particularly TDD and code review), there just aren't many type-related bugs left to catch (very near zero). Mileage can and does vary. Airbnb noted a significant benefit from TypeScript. I suspect you could reproduce Airbnb's results if you had a good design review process and poor test coverage. Lots of people share your views. A lot of people love using TypeScript because it feels satisfying and the intellisense you get with it is really nice. I'm not saying anybody is wrong for feeling that way -- only that on the projects we used it for, ROI was not good.