CodeIgniter vs other frameworks

[eluser]bcamp1973[/eluser]
I just stumbled across CI in my Googling and on initial review I'm impressed. However, I'm also very inexperienced with frameworks. I'm not a trained programmer. Just someone that picked up PHP and then Javascript...I hack my way through on a daily basis. My grasp of OO development in general is very minimal and my understanding of the MVC pattern isn't even worth mentioning. However, I'm determined to learn. On that note I have a question. Has anyone done a comprehensive comparison of the various PHP frameworks out there? How does CI stack up? I want to learn a framework and of course I want to choose the right one. Are there any limitations with CI that you're finding frustrating?

Cheers!

[eluser]Matthew Pennell[/eluser]
Ten different PHP frameworks compared.

[eluser]ELRafael[/eluser]
Do not trust 100% in that link.

Some frameworks had implemented more features. Like Symphony with Templates.

But with that list you can know others frameworks, and the best way to take a decision is: TRY!

We can't tell you which is the best for you. And comparison isn't the best way.

[eluser]Rick Jolly[/eluser]
CI might be the best framework for a beginner. It has a brilliantly simple (yet powerful and flexible) design. The documentation is unparalleled. The community is helpful.

[eluser]bcamp1973[/eluser]
I'm starting to come to the conclusion myself. Having a solid community is huge. The documentation also seems to be quite superior to other options I've reviewed. I'm really liking what I see!

[eluser]Chris Newton[/eluser]
Some of the other frameworks are more feature rich (in some respects) but not too many can hold a candle to CI's documentation. I personally use CI because it's simple, cleans up my code, simplifies a lot of the irritating things about PHP that I don't like (pagination, forms, data access) and doesn't require a command line utility. UGH. The last thing I want to do is go to the command line time after time to set up my framework.

CI doesn't do everything for you, but enough to really, really help when you're generating applications. The difference between before and after? Before; programs that worked, but were hopelessly procedural with little reusable code, crummy validation, and lots of hidden bugs. After; programs that have components that can be reused and the peace of mind knowing that from a form data validation standpoint, my bases are really covered. Apps take me less time, less hassle, and they're a lot better. I can work on them being *cool* instead of just functional.

[eluser]Derek Allard[/eluser]
well said mahuti!

[eluser]Toppy[/eluser]
An important thing for me is a level of stability in the core code.

For example, I've tried many PHP frameworks and a there are a good portion of them that are constantly changing and it becomes difficult to find articles, examples or existing code that actually works with the current release. Many may be feature rich but it becomes very difficult knowing how to code for the existing framework when there is no current documentation or workable code.

CI may not release often but it is very nice to know where you stand with everything and not spend hours troubleshooting something that you shouldn't even be wasting your time on.

[eluser]Michael Wales[/eluser]
In addition to all of the backwards compatibility, great documentation, and beautiful code standards everyone else has mentioned I just wanted to mention:

CI is the smallest (as in filesize) and fastest (as in execution time) framework available today. There are tons of benchmarks and articles that can show real numbers - just flex some Google-fu.