someguynamedmatt · November 9, 2017 19:16 · Nov 9, 2017 · Nov 9, 2017 · Nov 9, 2017 · Nov 9, 2017
diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -8,6 +8,8 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 
 Used by: Facebook...
 
+Created: 2014
+
 > PROS
 - 👍  Built by Facebook, just like React – _in practice, this doesn’t seem to provide a marked advantage for flow_
 - 👍  Babel integration
@@ -37,6 +39,8 @@ _Stats for past month: 215 merged PRs, 46 Proposed PRs, 440 closed issues, 215 n
 
 Used by: Lyft, Microsoft, Google, Asana
 
+Created: 2012
+
 > PROS
 - 👍  Out-of-the-box, first class VSCode integration
 - 👍  Easier to setup

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -13,6 +13,8 @@ Used by: Facebook...
 - 👍  Babel integration
 - 👍  No _real_ learning curve
 - 👍  Inference of types
+- 👍  support for JSX
+
 > CONS
 - 👎  No “out-of-the-box” integration with any editor
 - 👎  Poor error messaging
@@ -21,6 +23,7 @@ Used by: Facebook...
 - 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
 - 👎  `.js` files could be flow, could be normal JS – not obvious at a glance
+
 > MEHs
 - 👍 /👎  Flow is highly interested in creating a provably correct type system
 - 👍 /👎  ~400 typed third-party libraries
@@ -42,7 +45,6 @@ Used by: Lyft, Microsoft, Google, Asana
 - 👍  `.ts` files easy to distinguish between `.js` files
 - 👍  (as of 2.3) ability to type-check non-TS files with `--checkJs`
 - 👍  support for JSX
-- 👍  **DECORATORS** (syntactic sugar, but oh so sweet)
 - 👍  Babel integration
 - 👍  Native watch-mode (file specific)
 - 👍👍👍  ~3,000 third-party libraries

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -36,7 +36,6 @@ Used by: Lyft, Microsoft, Google, Asana
 
 > PROS
 - 👍  Out-of-the-box, first class VSCode integration
-- 👍  More community type offerings
 - 👍  Easier to setup
 - 👍  Used by default in Angular2
 - 👍  Helpful error messaging

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -8,19 +8,20 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 
 Used by: Facebook...
 
+> PROS
 - 👍  Built by Facebook, just like React – _in practice, this doesn’t seem to provide a marked advantage for flow_
 - 👍  Babel integration
 - 👍  No _real_ learning curve
 - 👍  Inference of types
----
+> CONS
 - 👎  No “out-of-the-box” integration with any editor
 - 👎  Poor error messaging
 - 👎  Poor tooling (Getting Flow to run is not easy)
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
 - 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
 - 👎  `.js` files could be flow, could be normal JS – not obvious at a glance
----
+> MEHs
 - 👍 /👎  Flow is highly interested in creating a provably correct type system
 - 👍 /👎  ~400 typed third-party libraries
 
@@ -33,6 +34,7 @@ _Stats for past month: 215 merged PRs, 46 Proposed PRs, 440 closed issues, 215 n
 
 Used by: Lyft, Microsoft, Google, Asana
 
+> PROS
 - 👍  Out-of-the-box, first class VSCode integration
 - 👍  More community type offerings
 - 👍  Easier to setup
@@ -45,10 +47,12 @@ Used by: Lyft, Microsoft, Google, Asana
 - 👍  Babel integration
 - 👍  Native watch-mode (file specific)
 - 👍👍👍  ~3,000 third-party libraries
----
+
+> CONS
 - 👎  Possible increased language complexity --> learning curve
 - 👎  In my experience there are frequent breaking changes from version to version (not sure if this is still a problem)
----
+
+> MEHs
 - 👍/👎  More frequent releases, this can introduce breaking changes
 - 👍/👎  Typescript is not interested in creating a “provably correct” type system – instead tries to strike balance between correctness and productivity
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -12,15 +12,15 @@ Used by: Facebook...
 - 👍  Babel integration
 - 👍  No _real_ learning curve
 - 👍  Inference of types
-
+---
 - 👎  No “out-of-the-box” integration with any editor
 - 👎  Poor error messaging
 - 👎  Poor tooling (Getting Flow to run is not easy)
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
 - 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
 - 👎  `.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
 - 👍 /👎  ~400 typed third-party libraries
 
@@ -45,10 +45,10 @@ Used by: Lyft, Microsoft, Google, Asana
 - 👍  Babel integration
 - 👍  Native watch-mode (file specific)
 - 👍👍👍  ~3,000 third-party libraries
-
+---
 - 👎  Possible increased language complexity --> learning curve
 - 👎  In my experience there are frequent breaking changes from version to version (not sure if this is still a problem)
-
+---
 - 👍/👎  More frequent releases, this can introduce breaking changes
 - 👍/👎  Typescript is not interested in creating a “provably correct” type system – instead tries to strike balance between correctness and productivity
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -9,17 +9,19 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 Used by: Facebook...
 
 - 👍  Built by Facebook, just like React – _in practice, this doesn’t seem to provide a marked advantage for flow_
+- 👍  Babel integration
+- 👍  No _real_ learning curve
+- 👍  Inference of types
+
 - 👎  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
-- 👍  Inference of types
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
 - 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
-- 👍  Babel integration
-- 👍  No _real_ learning curve
+- 👎  `.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
 - 👍 /👎  ~400 typed third-party libraries
 
 
@@ -36,17 +38,21 @@ Used by: Lyft, Microsoft, Google, Asana
 - 👍  Easier to setup
 - 👍  Used by default in Angular2
 - 👍  Helpful error messaging
-- 👍/👎  More frequent releases, this can introduce breaking changes
 - 👍  `.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
 - 👍  (as of 2.3) ability to type-check non-TS files with `--checkJs`
 - 👍  support for JSX
 - 👍  **DECORATORS** (syntactic sugar, but oh so sweet)
 - 👍  Babel integration
 - 👍  Native watch-mode (file specific)
-- 👎  Possible increased language complexity --> learning curve
 - 👍👍👍  ~3,000 third-party libraries
 
+- 👎  Possible increased language complexity --> learning curve
+- 👎  In my experience there are frequent breaking changes from version to version (not sure if this is still a problem)
+
+- 👍/👎  More frequent releases, this can introduce breaking changes
+- 👍/👎  Typescript is not interested in creating a “provably correct” type system – instead tries to strike balance between correctness and productivity
+
+
 ### Links
 
 - https://engineering.tumblr.com/post/165261504692/flow-and-typescript

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -44,7 +44,7 @@ Used by: Lyft, Microsoft, Google, Asana
 - 👍  **DECORATORS** (syntactic sugar, but oh so sweet)
 - 👍  Babel integration
 - 👍  Native watch-mode (file specific)
-- 👎  Possible increased language complexity => learning curve
+- 👎  Possible increased language complexity --> learning curve
 - 👍👍👍  ~3,000 third-party libraries
 
 ### Links

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -18,7 +18,8 @@ Used by: Facebook...
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
 - 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
-- 👍 Babel integration
+- 👍  Babel integration
+- 👍  No _real_ learning curve
 - 👍 /👎  ~400 typed third-party libraries
 
 
@@ -30,20 +31,21 @@ _Stats for past month: 215 merged PRs, 46 Proposed PRs, 440 closed issues, 215 n
 
 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, this can introduce breaking changes
-- 👍 `.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
-- 👍 (as of 2.3) ability to type-check non-TS files with `--checkJs`
-- 👍 support for JSX
-- 👍 **DECORATORS** (syntactic sugar, but oh so sweet)
-- 👍 Babel integration
-- 👍 Native watch-mode (file specific)
-- 👍👍👍 ~3,000 third-party libraries
+- 👍  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, this can introduce breaking changes
+- 👍  `.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
+- 👍  (as of 2.3) ability to type-check non-TS files with `--checkJs`
+- 👍  support for JSX
+- 👍  **DECORATORS** (syntactic sugar, but oh so sweet)
+- 👍  Babel integration
+- 👍  Native watch-mode (file specific)
+- 👎  Possible increased language complexity => learning curve
+- 👍👍👍  ~3,000 third-party libraries
 
 ### Links
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -6,6 +6,8 @@ _Built by Facebook_
 
 _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new issues, SO Questions ~0.9k_
 
+Used by: Facebook...
+
 - 👍  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
@@ -26,7 +28,7 @@ _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, 
+Used by: Lyft, Microsoft, Google, Asana
 
 - 👍 Out-of-the-box, first class VSCode integration
 - 👍 More community type offerings

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -14,7 +14,7 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 - 👍 /👎  Flow is highly interested in creating a provably correct type system
 - 👍  Inference of types
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
-- 👎  unused vars? “Use a linter” -flow dev :(
+- 👎  Does it detect unused vars? “No. Use a linter.” -A Flow developer response :(
 - 👎  non-native watch mode
 - 👍 Babel integration
 - 👍 /👎  ~400 typed third-party libraries

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -16,6 +16,7 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 - 👎  bug with JSX spread operator ( `<Component {...props} />` )
 - 👎  unused vars? “Use a linter” -flow dev :(
 - 👎  non-native watch mode
+- 👍 Babel integration
 - 👍 /👎  ~400 typed third-party libraries
 
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -6,16 +6,17 @@ _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
-
-- 👍 Inference of types
+- 👍  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
+- 👍  Inference of types
+- 👎  bug with JSX spread operator ( `<Component {...props} />` )
+- 👎  unused vars? “Use a linter” -flow dev :(
+- 👎  non-native watch mode
+- 👍 /👎  ~400 typed third-party libraries
 
 
 ## Typescript
@@ -35,6 +36,11 @@ Used by: Lyft, Microsoft, Google, Asana,
 - 👍 `.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
 - 👍 (as of 2.3) ability to type-check non-TS files with `--checkJs`
+- 👍 support for JSX
+- 👍 **DECORATORS** (syntactic sugar, but oh so sweet)
+- 👍 Babel integration
+- 👍 Native watch-mode (file specific)
+- 👍👍👍 ~3,000 third-party libraries
 
 ### Links
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -33,8 +33,8 @@ Used by: Lyft, Microsoft, Google, Asana,
 - 👍 Helpful error messaging
 - 👍/👎 More frequent releases, this can introduce breaking changes
 - 👍 `.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
+- 👍 (as of 2.3) ability to type-check non-TS files with `--checkJs`
 
 ### Links
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -41,4 +41,5 @@ Used by: Lyft, Microsoft, Google, Asana,
 - https://engineering.tumblr.com/post/165261504692/flow-and-typescript
 - https://jan.varwig.org/2017/02/15/flow-vs-typescript.html
 - https://eng.lyft.com/typescript-at-lyft-64f0702346ea
-- https://medium.com/@ckoster22/migrating-from-flow-to-typescript-b065796797db
+- https://medium.com/@ckoster22/migrating-from-flow-to-typescript-b065796797db
+- https://www.reaktor.com/blog/refactoring-30000-lines-js-types/
diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -31,7 +31,7 @@ Used by: Lyft, Microsoft, Google, Asana,
 - 👍 Easier to setup
 - 👍 Used by default in Angular2
 - 👍 Helpful error messaging
-- 👍 More frequent releases
+- 👍/👎 More frequent releases, this can introduce breaking changes
 - 👍 `.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

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -15,7 +15,7 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 
 - 👍/👎 Flow is highly interested in creating a provably correct type system
 
-- 👎 Inference of types
+- 👍 Inference of types
 
 
 ## Typescript

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -15,6 +15,8 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 
 - 👍/👎 Flow is highly interested in creating a provably correct type system
 
+- 👎 Inference of types
+
 
 ## Typescript
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -13,7 +13,7 @@ _Stats for past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new
 - 👎 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 correctness
+- 👍/👎 Flow is highly interested in creating a provably correct type system
 
 
 ## Typescript

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -38,4 +38,5 @@ Used by: Lyft, Microsoft, Google, Asana,
 
 - https://engineering.tumblr.com/post/165261504692/flow-and-typescript
 - https://jan.varwig.org/2017/02/15/flow-vs-typescript.html
-- https://eng.lyft.com/typescript-at-lyft-64f0702346ea
+- https://eng.lyft.com/typescript-at-lyft-64f0702346ea
+- https://medium.com/@ckoster22/migrating-from-flow-to-typescript-b065796797db
diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -4,7 +4,7 @@
 
 _Built by Facebook_
 
-Past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new issues, SO Questions ~0.9k
+_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_
 
@@ -20,7 +20,7 @@ Past month: 0 merged PRs, 30 Proposed PRs, 50 closed issues, 135 new issues, SO
 
 _Built by Microsoft_
 
-Past month: 215 merged PRs, 46 Proposed PRs, 440 closed issues, 215 new issues, SO Questions ~38k
+_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, 
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -2,37 +2,37 @@
 
 ## Flow
 
-Built by Facebook
+_Built by Facebook_
 
 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_
+- 👍 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
+- 👎 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 correctness
+- 👍/👎 Flow is highly interested in creating a provably correctness
 
 
 ## Typescript
 
-Built by Microsoft
+_Built by Microsoft_
 
 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
+- 👍 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
+- 👍/👎 Typescript is not interested in creating a “provably correct” type system – instead tries to strike balance between correctness and productivity
 
 ### Links
 

diff --git a/typescript-vs-flow.md b/typescript-vs-flow.md
@@ -0,0 +1,41 @@
+# Flow vs. Typescript
+
+## Flow
+
+Built by Facebook
+
+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 correctness
+
+
+## Typescript
+
+Built by Microsoft
+
+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
+
+- https://engineering.tumblr.com/post/165261504692/flow-and-typescript
+- https://jan.varwig.org/2017/02/15/flow-vs-typescript.html
+- https://eng.lyft.com/typescript-at-lyft-64f0702346ea
No results found