4 ms·
I worked with Typescript for 2 years, then worked with Flow for 2 years and now I'm back on Typescript working for a big company. I agree that Flow had better
by 4di 8y ago
I worked with Typescript for 2 years, then worked with Flow for 2 years and now I'm back on Typescript working for a big company.
I agree that Flow had better capabilities around soundness. But the tooling around Typescript really made me jealous, specifically in VSCode.
Near the end of working with Flow, Typescript was getting some cool capabilities like refactoring JSX for React apps.
Nowadays I can easily say that Typescript is a far better experience than Flow. There are updates every two months, adding some neat features that you might find in other languages.
Then you add in the power of surrounding tools and their ecosystems like TSLint and it really feels like a next-level coding experience where the tools start writing the mundane code for you, driven the core TS static analysis.
- wafflesraccoon 8y agoI'd agree with everything you've said. Flow isn't bad but after working with TypeScript I could never go back. You're spot on with the tooling and ecosystem.
- ggregoire 8y agoAlso, TypeScript has a roadmap and when you report a bug, the devs actually reply. Flow doesn't have any of that.
- fooey 8y agoand now TSLint is merging with ESLint so all that effort and rules duplication will be going away