<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jameslk</author><text>I have used both TypeScript (for multiple projects) and Flow (at Facebook). TypeScript is much more feature-rich and looser in strictness. In practice, this looseness has been preferable, as I&amp;#x27;ve seen many of my colleagues fighting Flow&amp;#x27;s type system vs TypeScript (prior to FB). In theory, perhaps Flow&amp;#x27;s type system prevents more bugs, but I&amp;#x27;ve sometimes seen it circumvented with hacks just to get past its strictness. TypeScript&amp;#x27;s ability to infer types seems much smarter than Flow&amp;#x27;s as well.&lt;p&gt;Besides that, TypeScript has much wider adoption and community support. Most issues I have with TypeScript I can find others who have had similar issues on the web, where as I can&amp;#x27;t say the same about Flow.</text><parent_chain><item><author>celestialjeu</author><text>Have you used flow at all in the past? If so what would you say the major differences are&amp;#x2F;how difficult was any process to convert over? I&amp;#x27;m a huge fan of having the types defined just from a documentation perspective nevermind bug catching and debugging and all that. I feel relatively agnostic about the particular thing we use to do it so I&amp;#x27;m curious as to what the differences are.&lt;p&gt;But yeah it really has improved my day to day immensely and I really feel the difference when I&amp;#x27;m working in legacy portions of our apps that pre-date the flow adoption.</text></item><item><author>_robbywashere</author><text>It&amp;#x27;s very nice to see all of this consolidation going on in the Typescript ecosystem. For example Babel 7 shipping with direct Typescript support back in August, &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blogs.msdn.microsoft.com&amp;#x2F;typescript&amp;#x2F;2018&amp;#x2F;08&amp;#x2F;27&amp;#x2F;typescript-and-babel-7&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blogs.msdn.microsoft.com&amp;#x2F;typescript&amp;#x2F;2018&amp;#x2F;08&amp;#x2F;27&amp;#x2F;types...&lt;/a&gt;&lt;p&gt;I am a Typescript convert myself and would suggest any daily JS developer give it an honest try.</text></item></parent_chain></comment><story><title>Future of TypeScript on ESLint</title><url>https://eslint.org/blog/2019/01/future-typescript-eslint</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>_robbywashere</author><text>I have never used Flow beyond a basic hello world. The syntax is very similar. Some of the nomenclatures vary. All and all they will both accomplish 99% of the same thing - statically typing a dynamic language. Which gives you much more code confidence, `foobar is undefined` is very less likely. self-documenting code. (see: vs-code intellisense) And code maintenance scale abilities currently not possible with such a loose language like javascript.&lt;p&gt;So I would say if you&amp;#x27;re interested pick one and dive in.&lt;p&gt;Right now typescript has a lot of community momentum: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;DefinitelyTyped&amp;#x2F;DefinitelyTyped&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;DefinitelyTyped&amp;#x2F;DefinitelyTyped&lt;/a&gt;&lt;p&gt;And an extremely fast, open sourced, plugin enabled editor, vs-code ftw! I am a convert after being a longtime diehard vim user. (vs-code has the best vim binding emulation I have ever used in a free open sourced editor)&lt;p&gt;Facebook is deprecating their flow atom editor plugin; nuclide - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fbopensource&amp;#x2F;status&amp;#x2F;1072928679695548416?lang=en&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fbopensource&amp;#x2F;status&amp;#x2F;1072928679695548416?...&lt;/a&gt;&lt;p&gt;This is all why I would choose typescript over flow if it were up to me. maybe a flow user can chime in.</text><parent_chain><item><author>celestialjeu</author><text>Have you used flow at all in the past? If so what would you say the major differences are&amp;#x2F;how difficult was any process to convert over? I&amp;#x27;m a huge fan of having the types defined just from a documentation perspective nevermind bug catching and debugging and all that. I feel relatively agnostic about the particular thing we use to do it so I&amp;#x27;m curious as to what the differences are.&lt;p&gt;But yeah it really has improved my day to day immensely and I really feel the difference when I&amp;#x27;m working in legacy portions of our apps that pre-date the flow adoption.</text></item><item><author>_robbywashere</author><text>It&amp;#x27;s very nice to see all of this consolidation going on in the Typescript ecosystem. For example Babel 7 shipping with direct Typescript support back in August, &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blogs.msdn.microsoft.com&amp;#x2F;typescript&amp;#x2F;2018&amp;#x2F;08&amp;#x2F;27&amp;#x2F;typescript-and-babel-7&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blogs.msdn.microsoft.com&amp;#x2F;typescript&amp;#x2F;2018&amp;#x2F;08&amp;#x2F;27&amp;#x2F;types...&lt;/a&gt;&lt;p&gt;I am a Typescript convert myself and would suggest any daily JS developer give it an honest try.</text></item></parent_chain></comment><story><title>Future of TypeScript on ESLint</title><url>https://eslint.org/blog/2019/01/future-typescript-eslint</url></story>