<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>thecombjelly</author><text>I would highly recommend chicken scheme for most projects. It isn&apos;t as mature as other ecosystems, but it is getting there fast and is already quite mature and practical. I&apos;ve used it to build multiple web apps/sites.[0][1]&lt;p&gt;Learn more about the features it provides: &lt;a href=&quot;http://wiki.call-cc.org/man/4/Getting%20started&quot; rel=&quot;nofollow&quot;&gt;http://wiki.call-cc.org/man/4/Getting%20started&lt;/a&gt;&lt;p&gt;An index of the many libs it supports: &lt;a href=&quot;http://wiki.call-cc.org/chicken-projects/egg-index-4.html&quot; rel=&quot;nofollow&quot;&gt;http://wiki.call-cc.org/chicken-projects/egg-index-4.html&lt;/a&gt;&lt;p&gt;Why another lisp? &lt;a href=&quot;http://wiki.call-cc.org/man/4/faq#why-yet-another-scheme-implementation&quot; rel=&quot;nofollow&quot;&gt;http://wiki.call-cc.org/man/4/faq#why-yet-another-scheme-imp...&lt;/a&gt;&lt;p&gt;Getting good performance: &lt;a href=&quot;https://news.ycombinator.com/item?id=5381472&quot; rel=&quot;nofollow&quot;&gt;https://news.ycombinator.com/item?id=5381472&lt;/a&gt;&lt;p&gt;[0] &lt;a href=&quot;http://thintz.com?hn=t&quot; rel=&quot;nofollow&quot;&gt;http://thintz.com?hn=t&lt;/a&gt;
[1] &lt;a href=&quot;https://a.keeptherecords.com/demo&quot; rel=&quot;nofollow&quot;&gt;https://a.keeptherecords.com/demo&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Chicken Scheme</title><url>http://www.call-cc.org/</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>tsewlliw</author><text>The absolute most interesting thing about Chicken Scheme is the way it does allocations and garbage collection. I&apos;ve wanted for a long time to make the time to add a always-on cpu and memory profiler to Chicken Scheme that just tallys the &quot;return&quot; addresses during the gc, meaning at each cg cycle you have a pretty darn good tracing profiler, and keeps the &quot;return&quot; addresses in cells when they are moved off stack, so at any moment you can blame your memory usage on particular code. Clearly you &lt;i&gt;could&lt;/i&gt; do this sort of thing with a lot of runtimes, but Chicken&apos;s design really lends itself to it.</text><parent_chain></parent_chain></comment><story><title>Chicken Scheme</title><url>http://www.call-cc.org/</url></story>