Say No to Composer!

Here's my reasoning...
1. Although I like the idea of help managing libraries, the implementation of Composer adds extra work which, in many cases, ends up costing more time than just managing your libraries.
2. I do not like the "disconnect" that happens with Composer.  One of my main reasons for using CodeIgniter is that it keeps you in touch with the code, and "install" just means placing code where you need it.  With Composer, there is a black-box sensation, where you install software and lose track of what's running on your application.
3. I am pretty confident that 5 years from now the development community will be done with Composer, just as we are now done with PEAR.  I've been coding for 25 years, and Composer feels to me like so many "breakthroughs" that are not destined to last.

1. Nope.  I have many composer libraries.  I import them into the vendor folder.  I then instantiate them into my code and I'm done.  I can now use the library.  Takes me 2 seconds to use something.  I don't need to maintain that library and I have saved myself a ton of work by not developing the wheel again.

2. Every library that I install.  I go through the code and I throughly test and ensure its working completely.  I haven't come across any instances where it's a blackbox/magic or doesn't work.  Maybe I'm using high quality packages?

3. Doubtful.  There are reasons why PEAR was abandoned.  But what is next?  The League?

I don't understand the rational here.  Really, I don't.