3 ms·

Ok, when Glimmer's motivation was only typechecking, why not just fb flow then?

• Etheryte 10y ago
  Having used both extensively, TS is simply the better choice. Flow has multiple large bugs and issues, which many would consider critical, open and unsolved on their GitHub repo for more than a year(!) [1][2][3]. [1] https://github.com/facebook/flow/issues/245 https://github.com/facebook/flow/issues/245 [2] https://github.com/facebook/flow/issues/869 https://github.com/facebook/flow/issues/869 [3] https://github.com/facebook/flow/issues/1528 https://github.com/facebook/flow/issues/1528
  • lfischer 10y ago
    I struggled with multiple blind spots in Flow in the past, but recently tried porting the same code to Flow and Typescript and I was surprised that Flow took less work than TypeScript. Flow 0.43.1 has become very fast and seems to need less type annotations compared to TypeScript with noImplicitAny enabled. I wonder whether Flow’s happily infers any without complaining or whether its program flow analysis remains more sophisticated.
• Rapzid 10y ago
  You say "just fb flow" as if it's the default choice. If I were looking at project and community momentum, tooling, and adoption then TypeScript would seem like the obvious choice. I'm curious why you think "why not just fb flow" for somebody who wants typed JS. It's certainly an option, but it hardly seems the go-to solution.