Conversation

Honestly I have been working on projects with flow for the past two years & the signal to noise ratio is atrocious. Most time is spent chasing non-issues stuck in its cache, micomanaging type imports or tricking it into accepting perfectly acceptable code. It just wastes my time.

Quote Tweet

Mikeal Rogers

@mikeal

· Jul 12, 2018

I looked into it and I still don't need type errors to make programs that work.

Sylvain Pollet-Villard

@SylvainPV

Jul 13, 2018

do you see a solution other than getting rid of flow ? it can't be so black and white

Tim Oxley

@timkevinoxley

Jul 13, 2018

I'm not sure a 3rd party bolting types onto JS is ever going to be a particularly great experience. Might be better off just using a compile-to-js/wasm language where the typing is there by design e.g. see

Quote Tweet

Brendan Zabarauskas

@brendanzab

· Jul 13, 2018

I wanted to like Flow, but the UX still needs work. Still find Rust, Haskell, Reason/OCaml, Elm, etc to be much more reliable tools. Hoping it doesn't turn too many folks off using type systems as a tool for crafting clean, understandable APIs. twitter.com/secoif/status/

Show this thread

Replying to

and

I had a friend who would only choose libraries that were built with Typescript or Flow in mind from the start, and he seemed to have a good experience. Without that it's too easy for devs to create confusing, hard-to-type APIs if they don't consider this from the start.

11:30 AM · Jul 13, 2018Twitter Web Client