<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>tdees40</author><text>&lt;i&gt;Sighs&lt;/i&gt;.  I wish Nimrod were more popular.  It seems like a better version of D.  But there can only be so many languages with a fully functioning ecosystem, and I just doubt Nimrod will ever get there.  It seems to be a one-man shop at this point (as this demonstrates):&lt;p&gt;&lt;a href=&quot;https://github.com/Araq/Nimrod/graphs/contributors&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Araq&amp;#x2F;Nimrod&amp;#x2F;graphs&amp;#x2F;contributors&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Nimrod by Example</title><url>http://nimrod-by-example.github.io/</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>eudox</author><text>I&amp;#x27;m afraid the memory management scheme might cause the Nimrod ecosystem to end up with too many libraries that require GC, and since the building blocks are already using it, why not use it yourself?&lt;p&gt;Either make it fully manual, or do something like Rust (No small feat). A GC you can switch on and off sounds like a good idea, but programmers don&amp;#x27;t keep half the promises they make (&amp;quot;It&amp;#x27;s just an MVP, I&amp;#x27;ll refactor it to use manual memory later&amp;quot;).</text><parent_chain></parent_chain></comment><story><title>Nimrod by Example</title><url>http://nimrod-by-example.github.io/</url></story>