Reasons I use Kohana over Codeigniter
I orginally discovered Codeigniter about 18 months ago and I was delighted to find a PHP framework that behaved largely intuitively to me. As I got used to its quirks and adapted it to better suit me, I happened across a forked project called Kohana. Having built a number of applications with Kohana, I have yet to feel the need to modify its default behaviour in any significant way. It just fits well with me.
These features are my favourite benefits of using Kohana over Codeigniter:
- Seperation of system files and static content by default. No extra work is needed to seperate your application files from the framework system files
- Static classes for helpers instead of functions, allowing logical grouping of utility functions.
- Does not break $GET variables. I don’t care what the CI proponents say, breaking $GET is unacceptable.
- The session driver can optionally use native sessions. An application on it’s own secure enviroment doesn’t need to worry about native session security like you do on shared servers.
- Supports only PHP5+; PHP4 is dead, and PHP6 is not too far off, it’s time to cast off the dead weight.
There’s plenty more things I like better in Kohana, but the 5 above will have to do for now.
Codeigniter does have one advantage, better documentation, but as Kohana matures so should its documentation.