Why you need a PHP composer?

Hello! I never used frameworks, all the projects I write myself (PHP) (of course, with their experience and with its comfortable for me structure), so it's hard to imagine why you need a composer in the past.
I understand that it will download some files, plugins, etc. But what's the point if I don't know where he downloaded them and exactly what he downloaded. And why is it important to use it... Because with the same success features download the files, without a lot of unnecessary files with the same plugin and throw it in the folder manually.
In General, this whole question: why download a bunch of junk files, not knowing how and where they are downloaded, instead of manually downloading, where I just download a few necessary files and connect them to the project.
And do we need compositor for bespoke projects?

Please do not kick, ask more no one...
June 14th 19 at 18:13
2 answers
June 14th 19 at 18:15
Oh, how much I've seen people "I have all the bikes our own, why would I want something else".
1. To put a care package in a single command – the most obvious. To the radio archives.
2. Update in a single command. With that, if something goes wrong you can quickly revert.
3. Based on third-party packages. Don't have to have multiple copies of the same library.
4. Convenient built-in autoloader.
5. Convenience sweep. The repository is stored only your own code, which quickly diploidy to the server, and there already are all the necessary dependencies.
June 14th 19 at 18:17
Composer is a tool for dependency management in PHP. It allows you to declare the library depends on your project and it will be managed (install / upgrade) them for you.


Of course, You can manually download and install/update, just one day You think "damn, what a fool I was..." and begin to use composer

Find more questions by tags Composer