Why the hate for CI still

Why I use CI (and have for a long time):

1. Dead easy to setup and use.
2. The separation of the MVC is brilliant, straight forward and works efficiently.
3. The flexibility to code custom solutions because the framework isn't in the way is huge.
4. I don't need to learn a slew of other tools, methods, syntax in order to create even the simplest of tasks (not that learning is bad, but learning a bunch of things for the sake of saving a few seconds to setup a framework seems stupid)
5. Limited dependencies. I never know where the client's server is going to be and the condition of it, virtually every time, however, CI just works.
6. It doesn't try to do everything for me. I write LOTS of custom code for the business needs of my clients, I don't need a framework that has a pre-defined way to accomplish something that I either need to re-do/over-write or create from scratch that will cause issues with the rest of the pre-made modules (and, also, causes other developers who only do it the 'normal' way to have issues)
7. Very few things I Want to do in CI that I can't.

CI isn't perfect (no framework is the best for every situation every time anyway) and could have some segments and OOP principals supported better, but - so far - no matter what the issue is, we're able to either use CI directly or code with CI, along side it, to get what we want done.

Since I deal with a team of people and several jr. coders, ramp up time is minimal, they spend time learning our system and not the framework which saves us considerable money.