views:

609

answers:

5

I've never used either before. I'm not a pro php programmer, but want to be. I like "state of the art" tools and code. Is there any reason I shouldn't go for Kohana? I noticed there were not books on amazon about kohana.

Input is appreciated!

A: 

Kohana is a more 'advanced' framework built on top of CodeIgniter. So CodeIgniter is more lightweight, and may be better suited for smaller projects, and if you want to do more of the coding yourself.

Also, Kohana only runs in PHP 5, where CodeIgniter is compatible with PHP 4

edit: Correction about Kohana, here's the info from wiki that caused my misunderstanding:

Kohana was originally created as a project fork[3] of the CodeIgniter PHP framework under the name Blue Flame. The principal reason for the fork was to create a more community-based web application framework as many users were frustrated with CodeIgniter's lack of bug fixes and inclusion of new features requested by the community

followed later by . . .

While the initial release of Kohana was essentially an improved version of CodeIgniter, by the end of 2007 the Kohana development team had released version 2.0 which was a complete re-write from the ground up. The new version 2.0 was strictly a PHP5 framework and has formed the basis for all other releases since.

I wasn't aware of this change.

GSto
Kohana is NOT "built on top" of codeigniter. It is based on it no CI code can be found there. And it is now rewritten in k3.
Thorpe Obazee
Whoa! Never knew that. I always thought that Kohana was a modified CI.
Jimmie Lin
A: 

Kohana is superset of CI. If you see the Kohana documentation, it says that it extends certain things from CI.

Sarfraz
+2  A: 

Kohana documentation is a bit more sparse than the excellent docs available for CI. Don't underestimate the benefit of good documentation ...

stef
+1 This is the reason I like CI over Zend or CakePHP. The documentation makes it so easy to find what you need.
mrinject
CI's very well documented. If I needed anything, the documentation would in 99% of the cases satisfy me.
Jimmie Lin
A: 

Before I jumped into a framework, I learned about php, and all of its OOP stuff. Naturally, since I'm new to the language, it was php 5. I tried CI, but the learning curve was too steep. Kohana is simple and similar enough that it makes sense. Just reading through Kohana's code has proven to me to be ample substitute for its lack of comprehensive documentation, which is improving. They are both beautiful frameworks, but it boils down to whether you prefer community vs stability and how big the php version issue is for you.

Max Bucknell
"community vs stability"? The are both on the CI side. Backwards compatibility is the only thing "bad" about Kohana, although I don't consider it THAT "bad".
Thorpe Obazee
+1  A: 

Kohana is great because it's community-supported. The docs aren't perfect, but they cover the core classes and libraries. BTW there's currently 2 versions in development-2.4 and 3.x. They both have cool stuff like the cascading file system which allows you to override pretty much everything, the DB abstraction, several ORM libraries etc. The community is really friendly. I would say go with Kohana.

th 2.3.4 docs are excellent. Too bad Kohana moves so fast, the docs can't keep up. 2.4 and 3.0 docs are getting better though.
Thorpe Obazee