<a href="https:&#x2F;&#x2F;www.drupal.org&#x2F;node&#x2F;1874530" rel="nofollow">https:&#x2F;&#x2F;www.drupal.org&#x2F;node&#x2F;1874530</a> everything in this (short) issue is a lie: submitted as &quot;Proudly Found Elsewhere&quot; when a significant portion of the code was written by the author of this issue, just submitted upstream and then pulled downstream (check @author tags, it&#x27;s right there but <a href="https:&#x2F;&#x2F;github.com&#x2F;symfony-cmf&#x2F;Routing&#x2F;commits&#x2F;master?page=9" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;symfony-cmf&#x2F;Routing&#x2F;commits&#x2F;master?page=9</a> also here for the sake of archives, commits start at 3b152c4) to avoid usual scrunity by downstream (ie the normal Drupal core review process). To avoid anyone catching this (and I haven&#x27;t caught it for a very long time) it was submitted on Dec 26 when everyone is obviously away.<p>&quot;I don&#x27;t believe CMF is as stable as Symfony core&quot; this is at best FUD, Symfony CMF won&#x27;t see a stable release for another ten months <a href="http:&#x2F;&#x2F;symfony.com&#x2F;blog&#x2F;the-symfony-cmf-released-its-first-stable-version" rel="nofollow">http:&#x2F;&#x2F;symfony.com&#x2F;blog&#x2F;the-symfony-cmf-released-its-first-s...</a> Symfony 2 core had several stable releases <a href="http:&#x2F;&#x2F;symfony.com&#x2F;blog&#x2F;symfony-2-1-3-released" rel="nofollow">http:&#x2F;&#x2F;symfony.com&#x2F;blog&#x2F;symfony-2-1-3-released</a> by this point.<p>I have no idea how the core committers didn&#x27;t catch all this -- but you can&#x27;t really blame them, there was a gigantic pressure to move ahead. And then based on this foundation, everything link related, inbound and outbound was converted to route names instead of paths which is a) absolutely unnecessary b) destroys performance.<p>Of course, there was history and reason trying to avoid review of this pile of code. Symfony, in general, is an extremely poor fit for Drupal: Drupal was a convention based system and Symfony is very heavily a config based system. The most obvious and very glarring misfit is hooks vs events and despite hooks being the central Drupal building block there never was a fundamental, through research as to what if anything to replace them with. Compare the scrutiny Symfony Foundation received in <a href="https:&#x2F;&#x2F;groups.drupal.org&#x2F;node&#x2F;167299" rel="nofollow">https:&#x2F;&#x2F;groups.drupal.org&#x2F;node&#x2F;167299</a> to how Symfony HTTP Kernel got added: via an admittedly &quot;off-the-cuff&quot; prototype <a href="https:&#x2F;&#x2F;groups.drupal.org&#x2F;node&#x2F;198538" rel="nofollow">https:&#x2F;&#x2F;groups.drupal.org&#x2F;node&#x2F;198538</a> . Note that I was trying to push back on this immediately with little success then or ever. So after shoehorning HTTP Kernel in over some bitterness and fighting it stands to reason the architect wants to avoid any scrutiny this pile of code would receive.<p>Ps. Events have so much overhead that by now Drupal only uses the interface for them as we rewrote the dispatcher to scale. Benchmarks at <a href="https:&#x2F;&#x2F;www.drupal.org&#x2F;node&#x2F;1972300#comment-9216069" rel="nofollow">https:&#x2F;&#x2F;www.drupal.org&#x2F;node&#x2F;1972300#comment-9216069</a> .