Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why We Chose TypeScript Over FlowType

eng.lyft.com

Post reply on HN
Print view View original

1–7 of 7 posts

Re: Why We Chose TypeScript Over FlowType

#2

Post by whatever_dude »

Pretty interesting numbers. FTA:

> StackOverflow questions: FlowType: ~900; TypeScript~38,000

> GitHub Issues: FlowType: ~1,500 Open, 2,200 Closed; TypeScript: ~2,400 Open, 11,200 Closed

> GitHub pull requests FlowType: ~60 Open, 1,200 Closed; TypeScript: ~100 Open, ~5,000 Closed

> npm download per month FlowType: ~2.9 million/month, TypeScript: ~7.2 million/month

Community size or StackOverflow questions or, well, "popularity" are not exactly what makes a language or platform _good_, but I usually find that everything else being equal, there's a direct correlation. It's much easier being part of an engaged community.

Re: Why We Chose TypeScript Over FlowType

#3

Post by msoad »

whatever_dude wrote: post #2

Pretty interesting numbers. FTA: > StackOverflow questions: FlowType: ~900; TypeScript~38,000 > GitHub Issues: FlowType: ~1,500 Open, 2,200 Closed; TypeScript: ~2,400 Open, 11,200 Closed > GitHub pull requests FlowType: ~60 Open, 1,200 Closed; TypeScript: ~100 Open, ~5,000 Closed > npm download per month FlowType: ~2.9 million/month, TypeScript: ~7.2 million/month Community size or StackOverflow questions or, well, "…

Yes, it makes it easier to find solutions to possible problems you might have. We can call it Googlability maybe?!

Re: Why We Chose TypeScript Over FlowType

#5

Post by bcherny »

whatever_dude wrote: post #2

Pretty interesting numbers. FTA: > StackOverflow questions: FlowType: ~900; TypeScript~38,000 > GitHub Issues: FlowType: ~1,500 Open, 2,200 Closed; TypeScript: ~2,400 Open, 11,200 Closed > GitHub pull requests FlowType: ~60 Open, 1,200 Closed; TypeScript: ~100 Open, ~5,000 Closed > npm download per month FlowType: ~2.9 million/month, TypeScript: ~7.2 million/month Community size or StackOverflow questions or, well, "…

Not to mention TypeScript has 10x the number of community typings as flow.

See slide here: https://bcherny.github.io/Talks/why-typescript/#31

Re: Why We Chose TypeScript Over FlowType

#6

Post by hobofan »

bcherny wrote: post #5
whatever_dude wrote: post #2

Pretty interesting numbers. FTA: > StackOverflow questions: FlowType: ~900; TypeScript~38,000 > GitHub Issues: FlowType: ~1,500 Open, 2,200 Closed; TypeScript: ~2,400 Open, 11,200 Closed > GitHub pull requests FlowType: ~60 Open, 1,200 Closed; TypeScript: ~100 Open, ~5,000 Closed > npm download per month FlowType: ~2.9 million/month, TypeScript: ~7.2 million/month Community size or StackOverflow questions or, well, "…

Not to mention TypeScript has 10x the number of community typings as flow. See slide here: https://bcherny.github.io/Talks/why-typescript/#31

Depending on what you work on, that can still be enough. I mainly used Flow in React (+ usual libraries) codebases, and was never missing any typings.

Re: Why We Chose TypeScript Over FlowType

#7

Post by bcherny »

hobofan wrote: post #6
bcherny wrote: post #5

Earlier quoted context omitted.

Not to mention TypeScript has 10x the number of community typings as flow. See slide here: https://bcherny.github.io/Talks/why-typescript/#31

Depending on what you work on, that can still be enough. I mainly used Flow in React (+ usual libraries) codebases, and was never missing any typings.

What sort of products did you work on? I often find that even with TypeScript I end up having to type a few libraries myself.
Post reply on HN