3 ms·
I agree. Type-related bugs of the kind that TS can catch are indeed rare and trivial. However, TS does help with documentation, intellisense and refactoring. Pe
by erokar 9y ago
I agree. Type-related bugs of the kind that TS can catch are indeed rare and trivial. However, TS does help with documentation, intellisense and refactoring. Personally, I will usually go with Babel/JS, since I don't find that the benefits of static typing outweigh the costs.
- emodendroket 9y agoI find the costs of static typing very low. What costs do you have in mind?
- martin_drapeau 9y agoEverything required to add that to regular Javascript: transpilation, extra markup and understanding and mastering a new tool. Another layer to manage and debug if you will.
- emodendroket 9y agoOh. But these days most JS projects are in some task runner anyway.
- mercer 9y agoAssuming you use ES6+ in production, so you need a build step anyways, would you still say TS adds costs that aren't worth it to you? And if so, which costs? I mean that in full honesty, as I generally find myself conflicted whenever I start a new project: TS or ES2015+?
- chr1 9y agoNow browsers support most of ES6, so you only need build step for deployments, and can have fast reloads without a build step when developing.