New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand on "typings for public libraries" #70
Comments
when you investigate using ts typings in flow, you learn that this won't really work as expected, because ts is not sound, there is not enough information in ts types to create flow types (because flow is sound). However, the inverse is easy, since flow types have more information. Perhaps, flow is best for hard-core libs that are used very widely, and ts is good for end-user programmers that aren't creating a quick hacky thing/need to make stable/robust software. |
TS: plenty of well maintained typings
Flow: a handful of mostly incomplete typings
For flow, this may be true for libraries but is an understatement for typings. Maybe this can be expanded to reference definitely-typed vs flow-typed.
Flow-typed is definitely lagging behind, but there's definitely support for commonly used libraries.
The text was updated successfully, but these errors were encountered: