pitching codeigniter to your boss or within your organization

[eluser]n0xie[/eluser]
1. Open Source.
2. Codebase thoroughly tested by an active community: self written code can be buggy.
3. Active development of the codebase by a company which has an economic interest in keeping the code lean,mean and clean. Their own core product expression engine runs on CI.
4. Security through many eyes: 0-day security issues will be spotted quickly. The fact that there hasn't been a security patch in a long long time is contest of the quality of the security. This doesn't mean it's flawless: it means that by default, if you know what you're doing, it's very very hard to find an exploit.
5. Rapid development: write less code. Less code means less chance of bugs, easier to maintain, easier to understand, easier to refactor.
6. MVC (this should really be a no brainer tbh). In all fairness, the MVC design pattern is thrown around while most frameworks use PAC including CI but that's just semantics.
7. Make a lot of task easy with use of basic helpers and libraries. Does not force you to use them (i.e. the procedural coders could just as easily write code the way they're used to).
8. Routes will save your life once someone in management hears this new buzz word called SEO.
9. Re-inventing the wheel is stupid
10. CodeIgniter is fast. Very very fast.

Fact is most arguments can be made for any open source framework be it Cake, Symphony, Zend or CodeIgniter (or any of the other PHP frameworks). Not using any of them is just plain silly if you're a webdeveloper. The reason I choose CodeIgniter is because the Core basically just gives you routes and a database abstraction. That's it. Which is great if you're experienced enough to write your own code. The power of CI is mostly how easy it is to overwrite default behaviour (extend core classes) and how little it gets in the way of you completing a task (hell even models are optional).

This gives you a tremendous amount of freedom, whilst making basic tasks very simple.