title: Why use a PSR-0 or PSR-4 autoload in composer if classmap is actually faster?
body: <p>I understand that you can use either a PSR standard to locate files, or tell composer a directory to scan for classes. <strong>The <a href="https://getcomposer.org/doc/04-schema.md#autoload">documentation recommends using the PSR-4</a> standard.</strong> There is also an option for composer to create an <a href="http://mouf-php.com/optimizing-composer-autoloader-performance">optimized autoloader, which basically generates a full classmap</a>. So why should one use PSR-4 at all if the best way to load is with a classmap?</p>
  
  <p>It makes sense to me to keep the directory structure, since that is a good way to organize anyway. However, it seems like the logical option would be to use PSR-4 loading on development machines, and then classmap for the production environment. That way, you don't have to rebuild your classmap every time you create a new class, but the production environment creates a complete one as a part of the deployment process without an additional call to </p>
  
  <pre><code>./composer.phar dump-autoload -o
  </code></pre>