Say No to Composer!

composer is a disaster that i specifically stay away from. oh god the dependencies. F@CK composer

Why is it a disaster?

dependencies have dependencies and those dependencies have deprecated or old versions of other libraries. and god forbid you want to use multiple versions of the same library. and then when it fails, it tells me to install bunch of sub dependencies manually. I suppose if you need some library that generates a simple form for you then sure it is not complicated but using it on an enterprise level projects, no thanks

So what's your alternative? Manage all the packages by hand?

What do you think people did before composer? Just not code? WHat kind of a question is that?

I should create my own spreadsheet lib, pdf, mail or template engine? reinvent the wheel... . dependencies  hell is not the fault of composer.

Think about what you just asked. Just because you shouldn't use a badly designed/used library manager doesn't mean you must write all of your libraries. What kind of a messed up logic is that?

Composer made the lives of unskilled coders a whole lot better because now they don't really have to know how to code. They just need to know how to put some libraries together. But for everyone else, it is a constant headache and a waste of time. You would spend less time downloading a library and putting a single line of include code in your project and viola! you are done. That library will stay exactly as is until you replace it with something. With composer, you cant even rely on it to install the same thing on 2 separate computers exactly the same. Adding a developer to an existing project and having them download the dependencies is such a waste of time because it never works the first time. NEVER