Kohana vs CodeIgniter… nowdays (2012)?

Here's my take on this: Of the TWO - not including other popular frameworks like zend and symfony I prefer the good ol habits of CI. HOWEVER I think kohana 3.0 or 3.1 is much easier to work with. I like the ORM interface a lot more than anything I used in CI, but that's just my preference.

I am a strong supporter of cached everything, so in the end my sites usually write html blocks to file and serve them with as little DB interaction as possible, so the overhead of Kohana's ORM system is a non-issue (not that I've heard much complaints anyhow). I never migrated to 3.2 because kohana just became too indecisive for me to care to support any further. We moved to symfony.

I would rather know one serious framework that maintains consistency well than to be forced to know the 3 major differences for one acceptable framework. I'm sure I will hear debates on this opinion. I never found the lack of support a huge problem because any competent programmer can figure it out with even the slightest nudges here and there.

Plus, stack overflow is an excellent resource so you are not likely to get stuck badly without some kind of option. So much as I know, Kohana attempted to take MVC and OOP "more seriously" however you want to define that, and from many programmers I've worked with it seemed to be praised as a more true framework. I know that doesn't help much but the arguments supplied were years ago and I just plain forgot why they preferred it since our projects were never really so huge that the performance differences, if any, would matter.

Why I like CI more - I use it as a flexible option and tend to not care for shortcuts. I see no solid benefit to database abstraction layers or anything fancy like Kohana's ORM and the seemingly clutterful model handling that is required to use it (also the ridiculous DB table naming conventions... pfft), though in the client based web world it is much faster than manually creating the queries as needed. I prefer CI routing system WAAAAAAY more than that utterly inferior joke introduced in kohana 3.1.Who knows how awful it became in 3.2. What was wrong with CI's routes?

I'm sure someone will tell. However, I must admit that the confusion of the routes do not interfere mostly and by default the undefined routing system nudges you in what could be considered the "proper" way to set up a controller... as in http://www.yoursite.com/controller/method/param. I see CI as plain jane and easy to use, configure and has plenty of documentation and support.

It has remained basically the same over the years.It wins my vote for a php framework I would use on my own private projects. I seem to be tangenting back on things to attack in Kohana, but in the end it is not like it is inconvenient. Both have done the job well and never choked when traffic spiked.

That could also be how they were used though, obviously. Plus, I think CI is easier to run with out of the box.

If you are confident on your code, don't use a framework. That's the beauty of PHP. Else you could use something a bit more sophisticated like: Python, Java or C#.

They will scale way better, in my opinion, if you think that your project will rapidly grow. Or you could read something about developers.facebook.com/blog/post/358/ ... Yeah! In the end the big bottleneck is still the database!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.