title: Downsides to Slim as a REST API framework
body: <p>I have been experimenting with Slim for a few days now and there is a lot that I like.  However, there is one thing that nags me - when Slim is used to build a REST API it insists on putting everything into one single .php file - or even worse, a load of anonymous functions (one for each exposed REST method).</p>
  
  <p>This works, that is not the issue.  However, does it not mean that when used for building any but the most trivial of APIs you are imposing an unnecessary burden on the server by getting it to load and parse a potentially really big PHP file when only a tiny percentage of its code is relevant?</p>
  
  <p>If <em>yes</em>, then it begs the next question - I am a newbie to micro frameworks - is there a micro framework that does things in a way that avoids this issue?</p>