<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>drinchev</author><text>I started 2 months ago a big project using TypeScript on NodeJS ( I&amp;#x27;m freelancer and I&amp;#x27;m building an API Service for a company ).&lt;p&gt;CONS:&lt;p&gt;1. Contribute a couple of times to DefinitelyType repo, because I needed definitions that doesn&amp;#x27;t exist or modify existing ones with their updated versions ( this is really pain in the ass at this point, because you will most certainly end up using definitions that either doesn&amp;#x27;t match your version number or are poorly written ).&lt;p&gt;2. Report a couple of bugs to WebStorm 10 team ( I&amp;#x27;m eagerly waiting for WS 11, which they say will improve the typescript support ).&lt;p&gt;3. Explain to my clients why I am using a beta version of a software for their precious product ( this is not a problem since today :) )&lt;p&gt;4. Sometimes the flexibility of typescript can slow you down a lot if you want to go deep with the proper typings and interface declarations. I actually spend a lot of time thinking how to organize my classes and interfaces now, instead of writing code.&lt;p&gt;PROS:&lt;p&gt;1. Code looks solid and professional ( CoffeeScript on the other - I was so much faster, but in the end I see not that easy readable code. )&lt;p&gt;2. Creating documentation is way easier ( using typedoc ). I never understood JSDocs as a pro and usually I spend lots of time on properly annotating, which is unneeded in TS.&lt;p&gt;3. There is no need to write `function(options) { if ( !options ) { throw new Error(&amp;quot;Options required&amp;quot;); } }`. this becomes `function(options : Object) {}`. This removes a lot of boilerplate and really cleans many of those typesafety checks from your code.&lt;p&gt;4. I&amp;#x27;m catching far more errors in the compilation phase than ever before ( see 3 ). I&amp;#x27;m also not writing any typesafety tests for my modules ( I was so happy, when I realised that! ).</text><parent_chain><item><author>unklefolk</author><text>I would be interested to hear other folks experience with TypeScript. We have move virtually all of the project I work on over to TypeScript but I am not seeing metrics improve (less bugs, quicker to fix etc). Gripes include lots of boilerplate TypeScript being generated and another learning curve for new starters (nearly everyone knows JS).&lt;p&gt;What are other folks experiences? Has it helped or hindered?</text></item></parent_chain></comment><story><title>Announcing TypeScript 1.5</title><url>http://blogs.msdn.com/b/typescript/archive/2015/07/20/announcing-typescript-1-5.aspx</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>timdumol</author><text>Moving to TypeScript definitely helped us. The move itself revealed a couple undefined variable errors, and static typing has saved us a lot of pain. It was also extremely useful for when we decided to remove a few libraries; the static typing gave us confidence that we didn&amp;#x27;t miss a few usages.</text><parent_chain><item><author>unklefolk</author><text>I would be interested to hear other folks experience with TypeScript. We have move virtually all of the project I work on over to TypeScript but I am not seeing metrics improve (less bugs, quicker to fix etc). Gripes include lots of boilerplate TypeScript being generated and another learning curve for new starters (nearly everyone knows JS).&lt;p&gt;What are other folks experiences? Has it helped or hindered?</text></item></parent_chain></comment><story><title>Announcing TypeScript 1.5</title><url>http://blogs.msdn.com/b/typescript/archive/2015/07/20/announcing-typescript-1-5.aspx</url></story>