<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>hcatlin</author><text>Wow, didn&amp;#x27;t expect to see this at the top of HN. Thanks kudo for promoting the project!&lt;p&gt;Aaron Leung and I have been working on this for a while. I&amp;#x27;m the original creator of Sass and Aaron is a badass computer linguist. Hoping to announce some big new features around the end of the year.&lt;p&gt;Official site is at: &lt;a href=&quot;http://libsass.org&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;libsass.org&lt;/a&gt;
Or, follow us on Twitter for more updates: @hcatlin &amp;amp; @akhleung</text><parent_chain></parent_chain></comment><story><title>Libsass – C implementation of a Sass compiler</title><url>https://github.com/hcatlin/libsass</url><text></text></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>danenania</author><text>This is great as compilation in ruby really is painfully slow for anything substantial, but I wonder about the choice of  an independent project vs. forking the ruby compiler and optimizing the bottlenecks with C extensions. Might that allow you to fix the most serious issues without having to worry about maintaining feature parity in a completely separate code base?&lt;p&gt;In any case, nice work. I look forward to trying it out in my next project.</text><parent_chain></parent_chain></comment><story><title>Libsass – C implementation of a Sass compiler</title><url>https://github.com/hcatlin/libsass</url><text></text></story>