<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>esamatti</author><text>It&amp;#x27;s worth noting that with upcoming Babel 7 it is possible to strip Typescript types like with Flow and use it just as a typechecker&amp;#x2F;linter [1]. This means following things:&lt;p&gt;- You don&amp;#x27;t need ts-loader&amp;#x2F;at-loader with Webpack anymore. You&amp;#x27;ll lose typechecking during webpack build but you can run it as separate step. Your editor will show them as usual still.&lt;p&gt;- You can use all the Babel plugins with Typescript without running two compilers (should speed things up)&lt;p&gt;- Should add first class support for React Native as it uses Babel (or at least no more 2-step builds)&lt;p&gt;[1]: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;babeljs.io&amp;#x2F;blog&amp;#x2F;2017&amp;#x2F;09&amp;#x2F;12&amp;#x2F;planning-for-7.0#typescript&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;babeljs.io&amp;#x2F;blog&amp;#x2F;2017&amp;#x2F;09&amp;#x2F;12&amp;#x2F;planning-for-7.0#typescrip...&lt;/a&gt;&lt;p&gt;EDIT: For the curious here&amp;#x27;s my build configuration with Webpack demoing this with extra plugins &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;epeli&amp;#x2F;bb8ae386f9dbb2a4ae2159e1f265fd56&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;epeli&amp;#x2F;bb8ae386f9dbb2a4ae2159e1f265fd...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Flow and TypeScript</title><url>https://engineering.tumblr.com/post/165261504692/flow-and-typescript</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>pcx</author><text>We faced a similar situation in our project and went with Flow instead. We found a TS + Webpack setup too unreliable. There are couple of popular Webpack loaders (ts-loader and at-loader), and both kept crashing the Node process every other build. Build times were pretty high. We could not find any documentation on how to fix these problems, except for a few open GitHub issues.&lt;p&gt;We then tried Flow. Oh dear god, has it been a blessing.&lt;p&gt;Pros:&lt;p&gt;* It&amp;#x27;s seamless to integrate with Webpack, ESLint &amp;amp; Babel.&lt;p&gt;* It&amp;#x27;s crazy fast&lt;p&gt;* Has great support for React&lt;p&gt;* Fits in perfectly with Redux&lt;p&gt;* Dead easy for beginners to learn&lt;p&gt;* Has an amazing Type system. My major experience with types has been Java, and Flowtype just blew my mind with - non-nullable types, subtyping and type refining.&lt;p&gt;* Documentation is great&lt;p&gt;* Community is very active&lt;p&gt;Cons:&lt;p&gt;* About 1&amp;#x2F;3rd of the time error messages are not intuitive. But nothing you can not figure out. And it&amp;#x27;s getting better.</text><parent_chain></parent_chain></comment><story><title>Flow and TypeScript</title><url>https://engineering.tumblr.com/post/165261504692/flow-and-typescript</url></story>