Say No to Composer!

@MatthewSchenker

Just saying "No" is the easiest thing. Is there something positive you can propose? You wrote "I am confident about the framework's future.". Ok, but do you see any details about this future? Or just CodeIgniter 3 is perfect for you?

------------------------------------------------------

There are two major problems to be solved:

1. CodeIgniter must recognize that PHP has true class autoloading feature. Its benefit about human productivity is obvious. How to be implemented? Not in the way Kohana tried in the past, they have invented their own autoloading system. Where is Kohana now?

Composer gives a de-facto standard. ZF3, Laravel, Symfony use it. You say "I am pretty confident that 5 years from now the development community will be done with Composer". What is the ground of your prediction? The analogy with PEAR is a quite weak argument. How the guys that have invested too much efforts will say "we don't like Composer" just like that?

2. The "God object" pattern - this is another topic.

Here is my alternative prediction: CodeIgniter will have its future if it has the desire to address at least these two key problems. The ground of this prediction is what competition achieves. They get improved, we think and talk too much about trivial things.

PS: For achieving autoloading, if somebody finds a way to trick $this->load->lang('language_file'); he/she will be the master of the Universe. :-)