Say No to Composer!

@MatthewSchenker

Sharing a hunch is not bad, sometimes decisions are made on this basis. To prove something is often hard and expensive.

Let me propose a speculation of mine. Many systems are using Composer and their architectures are quite different. To blame Composer for their success or failure seems to me exaggerated. Here is some criticism about Laravel http://archived.shift8creative.com/posts...ravel.html I don't see something that is caused solely by Composer (Edit: maybe "slow bootstrap" is for one). On other place (I can not find a link now) I saw that Laravel is criticized about its service locator pattern, which makes not easy to locate a certain fragment of code that actually does the real job.

My hunch is that mess (yes, I agree, there is mess) is caused not by Composer, but by patterns used. With or without Composer a critical architectural mistake might happen.