<story><title>Response to Netflix&apos;s “Node.js in Flames” Blog Post</title><url>https://gist.github.com/hueniverse/a3109f716bf25718ba0e</url></story><parent_chain></parent_chain><comment><author>hardwaresofton</author><text>I want to point out that in the thread here on HN (&lt;a href=&quot;https://news.ycombinator.com/item?id=8631022&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=8631022&lt;/a&gt;) about that Netflix article, the top comment debunks the myth that the list-of-handlers was the issue slowing them down.&lt;p&gt;While creating a grammar from the combination of the regular expressions (which is why you can&amp;#x27;t just have a hash) is definitely a solution (quite possibly THE solution), that&amp;#x27;s definitely not an MVP-type of solution, and is pretty non-trivial.&lt;p&gt;The actual problem was them constantly adding handlers by accident.&lt;p&gt;One of the reasons I love and use HN so much (I give almost no other site so much pull on my personal opinion) is that smart (or very careful and well-read dumb people) leave well-thought-out comments like the one I mentioned.</text></comment>
<story><title>Response to Netflix&apos;s “Node.js in Flames” Blog Post</title><url>https://gist.github.com/hueniverse/a3109f716bf25718ba0e</url></story><parent_chain></parent_chain><comment><author>ericHosick</author><text>&amp;gt; The criticism about allowing routes to repeat in the express array shows that even after doing all this work, the Netflix team still doesn’t understand how express works.&lt;p&gt;Wouldn&amp;#x27;t a better solution, in this context, be to aggregate values under the same key?</text></comment>