<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>dschiptsov</author><text>What is interesting here is to compare this one man&amp;#x27;s effort with &amp;quot;ancient tools&amp;quot; well-researched by two generations of old-school programmers with that amateurish hype and nonsense about node (author publicly stated in his blog that he has no experience with server side development on a POSIX system) and golang - a minimalist approach, carefully crafted by a rigorously trained &amp;quot;professionals&amp;quot;. It is not just about KBs and milliseconds.&lt;p&gt;Btw, this &amp;quot;Hello world&amp;quot; example tells a little, basically, how efficiently memory allocation, and IO layer are implemented (that&amp;#x27;s why no one still could beat nginx).&lt;p&gt;Much more interesting comparison would be of some &amp;quot;real-world scenario&amp;quot;, say, &amp;quot;implement an http look up for some public data-set, imported into a &lt;i&gt;persistent&lt;/i&gt; local storage, say, Postgresql&amp;quot; and then compare not just throughput rates, but  also resource usage.</text><parent_chain></parent_chain></comment><story><title>Woo: Fast HTTP Server in Common Lisp</title><url>https://github.com/fukamachi/woo</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>kjksf</author><text>It&amp;#x27;s not really written in Common Lisp.&lt;p&gt;&amp;quot;built on top of libev&amp;quot;&lt;p&gt;The lisp part is a thin ffi wrapper on top of lots of C code.&lt;p&gt;Not than an ffi wrapper around C code isn&amp;#x27;t useful, but it&amp;#x27;s C code that does all the heavy lifting there.</text><parent_chain></parent_chain></comment><story><title>Woo: Fast HTTP Server in Common Lisp</title><url>https://github.com/fukamachi/woo</url></story>