views:

44

answers:

3

I've been searching for a framework for the past couple weeks and I must say it's not bee very good. So far I've tried

  • Code Igniter
  • Kohana
  • Dingo

Looked at (started to try)

  • Symphony
  • Yii

and read up on many others but I can't seem to find one that I find usable.

Usable for me being simplistic in the CI and Kohana sense, i.e more minimalist. The listed frameworks are those I like but I can't get a feel for Yii and Symphony. CI feels a little verbose especially when compared to Dingo but both Dingo and Kohana and underdocumented which is a majour turnoff.

From what I can see out there, the frameworks that people like to recommend are not well documented, e.g picking on Kohana, the available documentation is totally useless because it's not for the latest release it just leave the feeling that people don't actually use these things.

Some that looked good but dead or will likely die:

  • Recess
  • Not sure What's hapenning with Doo

So to the main question: What are some PHP frameworks that are well documented, lightweight(No Cake, Zend) and that people actually use?

A: 

I personally use the Nette framework - clean, small, extremely useful, you can use only the parts of it you like and a very good documentation: http://nette.org/en/

dark_charlie
+1  A: 

Personally, I really like Lithium. It's 5.3 only, but it's really powerful. It's architected REALLY well (IMHO) and is fairly light. But it does fail your documentation test (And fail hard at that). But I have found that the devs do hang out on IRC and are pretty accepting of new users, so if you don't understand something, there is a source for answers...

ircmaxell
A: 

The best compromise (yes I said compromise) between features, documentation, and community, is Yii.

I will give you a simple exercise wich I think is representative of the general experience you will have with each respective framework: try to implement htmlpurifyer in Yii, kohana, etc. (I wanted to implement it for real, not as an exerise, but I think the experience is representative).

With google I found a topic on the yii forum about htmlpurifyer. I also found one in the kohana forum. At first glance no big difference, but once you actually try to implement and use it, aaaa, big difference.

Kohana has cleaner coding style / architecture, but the lack of documewntation is crippling (this could be solved if you arent shy about using their forum... EVERY DAY - THIS IS NOT A JOKE). You will make fast progress for a while in your develpopment with kohana and be really impressed an pleased with it, and then hit a deadspot in the documentation (including google), and all the time you gained untill now, and all thew joy will be tripply lost on the issue you hit because of the lack of documentation.

This problem will never go away in my opinion (unfortunately), because alot of the contributions from the community to Kohana (modules and stuff) are made in github style, with the only documentation being a short introduction (at best).

In order for this problem to go away, the devs would have to encourage somehow the contributors to up their documentation standard. But this isnt going to happen because the devs themselves use the same style of contribution to kohana (github projects with sparse documentation). So even if tthey fix the main documentation, and make it 100% bulletproof, there will still be the comunity contributions which will have bad docs, or you will have to create the whole module from scratch yourself.

snrp