Continuing the discussion from Remove "disabled" packages feature:
I can see the caching argument, but what is it that we actually need and which we don’t know anyway in the class loader for example? I’d be happy to get some examples.
For things not being installed via composer, that’s actually the norm I’d say. The original usecase for composer is to pull in 3rd party libs to be used together with your application, and that is more often than not just a bunch of code, and not a composer package on it’s own. So it seems 99% of the people just pull in those libraries, require the
autoload.php composer generates and are done with it. What else do we need on top of that?