<story><title>Github: CoffeeScript cracks the top 10 languages </title><url>https://github.com/languages</url><text></text></story><parent_chain></parent_chain><comment><author>jashkenas</author><text>Whoops -- cancel the party folks. Apparently the rankings just count the percentage of GitHub repos with &lt;i&gt;any&lt;/i&gt; amount of the language in it. I bet CoffeeScript&apos;s recent rise has a lot to do with a handful of auto-generated-by-default files in Rails projects.&lt;p&gt;Source: &lt;a href=&quot;https://twitter.com/joshpeek/status/205783659830198273&quot; rel=&quot;nofollow&quot;&gt;https://twitter.com/joshpeek/status/205783659830198273&lt;/a&gt;</text></comment>
<story><title>Github: CoffeeScript cracks the top 10 languages </title><url>https://github.com/languages</url><text></text></story><parent_chain></parent_chain><comment><author>timr</author><text>I don&apos;t get it.&lt;p&gt;I&apos;m in the process of ripping the last bit of coffeescript out of our code.  The marginal benefits of the language don&apos;t exceed the costs of having another build dependency, and another syntax to understand.  For daily work, I &lt;i&gt;already&lt;/i&gt; have to switch contexts between Javascript, CSS, SCSS, HTML, rHTML, HAML and Ruby (not to mention other &lt;i&gt;tools&lt;/i&gt; like Bash, Rake, etc., along with API knowledge like the Rails API, jQuery, and all of the various un- or poorly-documented gems).  Ultimately, it&apos;s a huge mental burden.  Every new thing is a &lt;i&gt;new thing&lt;/i&gt; that someone has to understand to be productive.&lt;p&gt;To justify the extra mental cost of another piece of technology, it has to do something pretty amazing.  A minor syntactical transformation of javascript just doesn&apos;t cut it.</text></comment>