[MrFantsyPants]

I've been working on a symfony project for the last six months, and after it ends, I hope to never see it again. Over-engineered fits, but I also have issues with many of their choices. In the end, I would have built a better product in the time allotted using something else, even my own primitive codebase.

Having come to know it pretty damn well, I'd have trouble recommending it to anyone else.

[pauljonas]

I looked at Symfony, CakePHP, and a few others (at time, Zend was not anywhere near production ready), and all just seemed like (a) overkill or (b) inadequate. In the final analysis, I wrote my own framework.

On the flip side, homebrew framework development has become a larger project in recent years. Nowdays, you need to include in AJAX integration, slicker client UI, mobile phone accommodation, web services API, multimedia handling, etc.... And you're going to be reliant on 3rd party libraries that you need to research, choose, perhaps configure and upgrade at intervals.

Have used Rails for a few projects and it provided a constant stream of annoyances as anytime you attempted to do something that didn't quite fit into the DHH "vision", it was a hassle. Though I liked the DB migration setup in spite of the lock in to autoincrement integer keys.