<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>bkjelden</author><text>I would encourage anyone looking at a C# to javascript compiler to check out typescript first.&lt;p&gt;I&amp;#x27;ve seen projects use a compiler similar to this, and while writing C# sounds great to developers who already know C#, the differences between the C# source and the generated JS make debugging and maintenance difficult.&lt;p&gt;In my experience typescript provides C# developers much of what they are looking for - type safety, familiar class definitions, etc - while still being very easy to debug.</text><parent_chain></parent_chain></comment><story><title>Show HN: C#-to-JavaScript compiler powered by Microsoft Roslyn</title><url>http://duoco.de</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>j_s</author><text>SharpKit has a 3+ year head-start selling and supporting their solution (available commercially and under GPL3). I have no doubt they have considered transitioning to Roslyn as well; it is a tough decision for all those who had already built a C# parser. (Note that those using Mono [Saltarelle for sure] will wind up stuck unless they follow along to Roslyn.)&lt;p&gt;The biggest part of these projects is the re-implementation of the .NET CLR in JavaScript (for example, Saltarelle began life using the Script# runtime with a few tweaks). The more production usage the runtime has seen, the more useful the translation tool becomes!&lt;p&gt;&lt;a href=&quot;http://sharpkit.net/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;sharpkit.net&amp;#x2F;&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Show HN: C#-to-JavaScript compiler powered by Microsoft Roslyn</title><url>http://duoco.de</url></story>