Picking Flow in 2018 is a bad idea imo.
It's not strictly a shot in the foot, as the two are extremely similar, so the knowledge is portable, but:
It's a worse experience, especially if you are addicted to VS Code
There are less type definitions available (both community ala @types/ and built in).
These two hit newcomers especially hard and might discourage them from typed JavaScript, which is really the only type of handwritten JavaScript one should be doing.
Source: I've used both to the limit.
Also, some will say that flowtype is more functional and TypeScript is more Object-Oriented. Besides like two keywords of syntax that is a lie and just a way to drag TypeScript through the mire. Both use duck/structural typing, and both can usually fully type your higher order functions with comparable verbosity.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Picking Flow in 2018 is a bad idea imo.
It's not strictly a shot in the foot, as the two are extremely similar, so the knowledge is portable, but:
@types/and built in).These two hit newcomers especially hard and might discourage them from typed JavaScript, which is really the only type of handwritten JavaScript one should be doing.
Source: I've used both to the limit.
Also, some will say that flowtype is more functional and TypeScript is more Object-Oriented. Besides like two keywords of syntax that is a lie and just a way to drag TypeScript through the mire. Both use duck/structural typing, and both can usually fully type your higher order functions with comparable verbosity.