News for hackers. Stuff that matters.

A comment on Porting a React Front End to TypeScript. Parent comment

Re:Porting a React Front End to TypeScript by jeswin on Tuesday April 28, 2020 @02:36AM (#23004121)
A big benefit with static typing is the ability to refactor easily. It takes time to get design and code right, in a way that captures the requirements well as well as code quality. With static typing, you get immediate feedback while you tune your code.

Most of the popular large JS projects have switched (or are switching) to TypeScript (or Flow for React, though they'd have used TypeScript today). So that supports the argument in favor of TypeScript.

[ Parent | on HN ]
Re:Porting a React Front End to TypeScript by joelbluminator on Tuesday April 28, 2020 @02:41AM (#23004152)
I don't know the js world that well, can you provide links that show most js developers use typescript? There are arguments for both. There are still millions of python/php/js/ruby devs and codebases that use dynamic code. It could be that in javascript the gains of types are more felt than in Ruby/Python. '' + [] will raise an error in Ruby and probably python too.
[ Parent | on HN ]
Re:Porting a React Front End to TypeScript by angus_gh on Tuesday April 28, 2020 @11:06AM (#23007692)
> can you provide links that show most js developers use typescript?

They didn't say most developers had switched, they said most large projects have switched

[ Parent | on HN ]