News for hackers. Stuff that matters.
Re:Why We Chose Typescript by emodendroket on Saturday July 01, 2017 @09:02AM (#14676931)
I find the costs of static typing very low. What costs do you have in mind?
Re:Why We Chose Typescript by martin_drapeau on Saturday July 01, 2017 @09:06AM (#14676945)
Everything 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.
Re:Why We Chose Typescript by mercer on Saturday July 01, 2017 @09:33AM (#14677038)
Assuming 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+?
Re:Why We Chose Typescript by chr1 on Saturday July 01, 2017 @11:12AM (#14677431)
Now browsers support most of ES6, so you only need build step for deployments, and can have fast reloads without a build step when developing.
Re:Why We Chose Typescript by emodendroket on Saturday July 01, 2017 @09:25AM (#14677008)
Oh. But these days most JS projects are in some task runner anyway.