[seattle_spring]

> Flow is more like a side project that is completely getting out of hand.

Flow is used on all of Facebook's modern internal front-end code, and has a dedicated team maintaining it. They release major bugfixes and new features on an almost weekly cadence.

The "issues" count above is the 3rd party library definitions, which I don't think Facebook involves themselves too much in. The community for TS is larger, so therefore more issues will be found and fixed.

[qudat]

I disagree. I've used both Flow and Typescript for a few major projects. I was able to resolve virtually all of my Typescript issues by googling. Flow on the other hand required many github issues and most of them were ignored or unresolved. In my mind it's a no-brainer, Flow is dead and mostly unmaintained from an open-source point of view. I'm sure the Flow team is great but they only care about one consumer, the Facebook.

They should slap an unmaintained notice in their project and direct people to Typescript and save everyone a whole lot of hassle, including themselves.

That isn't to mention the third-party type definitions are completely lacking on the Flow side.

Flow is dead.

[seattle_spring]

What do you disagree with, exactly? You just said, "I disagree", and then wrote a bunch of unrelated stuff.

Sorry that you had a bad experience. I've been using Flow for more than 2 years now and couldn't be happier.

What does "unmaintained" mean to you? Other than during Christmas, they release almost every single week [1].

[1] https://github.com/facebook/flow/releases