I don't think that shift towards ORM is a bad choice. The Model Layer of CakePHP was quite staightforward, but it lacked efficiency in terms of readibility and flexibility. The implementation of ORM might frighten the old folks, accustomed to Active Record Queries, but in the end its a step forward, which will bring more developers, who are already using these tehcniques. Whether we like it or not, more data abstraction will be applied as the tools we use and programms we write become more complex and powerfull. A few drawbacks i have to mention about new version are competitiveness and community scale. Frameworks like Symfony2 have already a large community which provides a great number of standard components (called bundles) for various types of web applications. I think it would be tough for CakePHP to compete with other frameworks, which implemented similar techniques a long time ago and already built an extensive community around that. But the one thing that still encourages me to use CakePHP is it's strcuture that speaks to the core of issue you are trying to solve, an approach to problem not as a developer but a problem solver. I hope we will love to use CakePHP for a long time.
-- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
