WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36335, comment 207


Ignore:
Timestamp:
09/24/2016 06:24:21 AM (4 years ago)
Author:
schlessera
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36335, comment 207

    initial v1  
    2121* only seemingly adds one perceived advantage of its own (tightly optimized custom autoloader), which is not really an advantage, because you can generate this exact same autoloader with Composer Autoloader Generator.
    2222
    23 Unless I'm missing something crucial, and don't see in what ways this solution would be preferable.
     23Unless I'm missing something crucial, I don't see in what ways this solution would be preferable.
    2424
    2525@TJNowell If anyone wants to play around with benchmarks, please go ahead. I personally will not waste time with benchmarks right now. If the goal is to see what autoloader '''implementation''' is faster, then this has nothing to do with Composer/no-Composer. And if the goal is to see whether an autoloader even makes sense in the first place, then I'm baffled, and must admit that we will never find out, because first of all the benefits are not only about performance, and secondly, we would need to implement it and optimize Core for it first to get proof. So, in essence we're trying to benchmark the chicken and egg problem.