I've used Flow in 2016 and getting it to work on code editors was a huge pain. Coworkers asked me weekly how to fix their environment to get it to work.
In 2017 I introduced TS to the codebase and never looked back. It just works™.
> I've used Flow in 2016 and getting it to work on code editors was a huge pain.
Typescript also has support for js-doc style type declarations, at a basic level, IMHO it's less painful to use than Flow. Does Flow even has a compiler that doesn't rely on OCaml?
I actually use JSX without React thanks to Typescript, I wrote an HTML builder myself (anybody can write one, it's easy) and it's quite handy since I don't have to rely on any framework/view library anymore.
7 comments
[ 2.7 ms ] story [ 16.9 ms ] threadAlso worth mentioning that TS npm download is greater than React consistently.
http://www.npmtrends.com/typescript-vs-react-vs-vue-vs-flow-...
I've used Flow in 2016 and getting it to work on code editors was a huge pain. Coworkers asked me weekly how to fix their environment to get it to work.
In 2017 I introduced TS to the codebase and never looked back. It just works™.
It is one of the things I have noted to look into next too.
Typescript also has support for js-doc style type declarations, at a basic level, IMHO it's less painful to use than Flow. Does Flow even has a compiler that doesn't rely on OCaml?
https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-i...
Yes but since I use Typescript static analysis as well: 2 birds, one stone.