Re:Announcing TypeScript 2.1
by wereHamster on Wednesday December 07, 2016 @01:55PM
(#13125109)
TypeScript doesn't split the community any more than Flow does. TypeScript remains very close to ES2016/2017, syntax-wise, with the only major difference being type annotations, but you have those with flow as well. Anybody who can read JavaScript can read TypeScript.
[ Parent
| on HN ]
Re:Announcing TypeScript 2.1
by thejameskyle on Wednesday December 07, 2016 @03:03PM
(#13125706)
Flow tries to integrate with the existing ecosystem as much as possible. By taking advantage of Babel, ESLint, Atom, etc.
With Flow you don't even have to opt-in to a new syntax. You can just use comments:
function foo(val /* : boolean */) /* : string */ {}
Using really powerful inference you can also write much fewer types. If you have well types libraries [you sometimes don't need types in your code at all](https://medium.com/@thejameskyle/flow-mapping-an-object-373d...).> With Flow you don't even have to opt-in to a new syntax. You can just use comments:
So you use a opt-in comment-based syntax instead of a opt-in non-comment based one for type-annotations.
Hardly a big difference.
> Using really powerful inference you can also write much fewer types
I'm just going to assume you didn't know typescript does this too.
Typescript is nice. You should give it a try once. You may end up surprised:)
Comments don't change it from being valid javascript whatsoever.