News for hackers. Stuff that matters.
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...).
Re:Announcing TypeScript 2.1 by josteink on Wednesday December 07, 2016 @04:02PM (#13126192)
> 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:)

Re:Announcing TypeScript 2.1 by coltonv on Saturday December 10, 2016 @12:02AM (#13144135)
Comments don't change it from being valid javascript whatsoever.
Re:Announcing TypeScript 2.1 by djmashko2 on Thursday December 08, 2016 @02:23AM (#13128927)
> By taking advantage of Babel, ESLint, Atom, etc.

Doesn't TypeScript actually predate all of those tools? So that logic doesn't seem reasonable.