Skip to content

Instantly share code, notes, and snippets.

@briangonzalez

briangonzalez/typescript-vs-flow.md

Last active November 3, 2017 17:11
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save briangonzalez/9c231d4648d5fbb061500ecc40ecf2f3 to your computer and use it in GitHub Desktop.
Save briangonzalez/9c231d4648d5fbb061500ecc40ecf2f3 to your computer and use it in GitHub Desktop.
Download ZIP
Typescript vs. Flow
Raw
typescript-vs-flow.md

Flow vs. Typescript

Flow

Built by Facebook

Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new issues, SO Questions ~0.9k

  • 👍 Built by Facebook, just like React – in practice, this doesn’t seem to provide a marked advantage for flow

  • 👎 No “out-of-the-box” integration with any editor

  • 👎 Poor error messaging

  • 👎 Poor tooling (Getting Flow to run is not easy)

  • 👎 .js files could be flow, could be normal JS – not obvious at a glance

  • 👍/👎 Flow is highly interested in creating a provably correct type system

Typescript

Built by Microsoft

Stats for past month: 215 merged PRs, 46 Proposed PRs, 440 closed issues, 215 new issues, SO Questions ~38k

Used by: Lyft, Microsoft, Google, Asana,

  • 👍 Out-of-the-box, first class VSCode integration

  • 👍 More community type offerings

  • 👍 Easier to setup

  • 👍 Used by default in Angular2

  • 👍 Helpful error messaging

  • 👍 More frequent releases

  • 👍 .ts files easy to distinguish between .js files

  • 👍/👎 Typescript is not interested in creating a “provably correct” type system – instead tries to strike balance between correctness and productivity

Links

@someguynamedmatt
Copy link

@briangonzalez Forkin' dis. Much respect, many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment