Brendan Zabarauskas on Twitter

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.

Quote Tweet

Tim Oxley

@timkevinoxley

· Jul 13, 2018

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. twitter.com/mikeal/status/

Show this thread

2

Brendan Zabarauskas

@brendanzab

Jul 13, 2018

I think one of the issues is that many of the JS APIs were hideously complex to begin with, and the types just expose this in an obvious way. React-redux's `connect` function is a terrible offender in this regard: github.com/flow-typed/flo

1

Brendan Zabarauskas

@brendanzab

One trick I learned for Flow off

@ur_friend_james

: don't use `any` unless you want implicit conversions (ack!) - used `mixed` instead, and then you have to an explicit cast.

4:51 AM · Jul 13, 2018Twitter Web Client

1

Like

Conversation