I'm curious what people think about the ways to get stronger typing in JavaScript. Vote what what you like to use, or would use if you were starting a new project.
I've been a strong proponent for Typescript since it's original public release and continue to be excited with updates in each new version as well as changes in the larger ecosystem. (The tool called "typings" is a new must have, doing a better job of typing information package manager than previous tools, for instance.)
I do think typing in general "lifts all boats" and its great to see some convergence work going on between Flow and Typescript. It's good to see typing work in one help provide typing work in the other. It's also good to think that both typing ecosystems are working to help build whatever the future of JS (EcmaScript) might be with regards to types. Where ES4 failed to top-down add types to the language spec, maybe Typescript and Flow can bottom-up add types to the language spec, even if maybe it just ends up being a sort of "Python typing compromise" where browsers have to accept the typing syntax but don't have to do anything with it.
That said, I do think that Typescript is superior than Flow for my workflows and for the productivity gains I get from Typescript specifically. The IDE experience when working with Typescript is fantastic. Typescript's ability to take ES2015 and ES2016 syntax, appropriately downlevel it to ES5 or remodularize it (convert ES6 modules to AMD/UMD) certainly comes in handy and can mean less reliance on Webpack or Babel in your tool chain. (Typescript's new JS input features expand this ability to fill a Webpack or Babel role. There's even proposals for Typescript to help link in CoreJS polyfills, furthering Typescript's ability to do what Babel does for you.)
Primarily I use Visual Studio. I'm still often asked to use C# (ASP.NET) backends and Visual Studio is great top to bottom with that stack.
I increasingly use Visual Studio Code (http://code.visualstudio.com/) for small projects or quick project tweaks and bug fixes. VS Code is just as strong an IDE for Typescript as VS proper.
5 comments
[ 3.0 ms ] story [ 20.6 ms ] threadThat said, I do think that Typescript is superior than Flow for my workflows and for the productivity gains I get from Typescript specifically. The IDE experience when working with Typescript is fantastic. Typescript's ability to take ES2015 and ES2016 syntax, appropriately downlevel it to ES5 or remodularize it (convert ES6 modules to AMD/UMD) certainly comes in handy and can mean less reliance on Webpack or Babel in your tool chain. (Typescript's new JS input features expand this ability to fill a Webpack or Babel role. There's even proposals for Typescript to help link in CoreJS polyfills, furthering Typescript's ability to do what Babel does for you.)
I increasingly use Visual Studio Code (http://code.visualstudio.com/) for small projects or quick project tweaks and bug fixes. VS Code is just as strong an IDE for Typescript as VS proper.