I agree with you!!! Em domingo, 5 de janeiro de 2014, bbf escreveu:
> This is the first time I've read about the reasoning behind the major > changes to 3.0. (for background I've been coding PHP since 1999, using Cake > since 2008, and "cakephp" is the only tag I follow on Stackoverflow ;) ) > > What are the strategic goals of Cake v3? > Grow adoption of the framework be switching to "more modern" features? Do > you feel more developers will give it a chance because it supports features > like traits, closures and an object-oriented ORM? I'm trying to understand > why all the breaking changes are being introduced. > > > What are the benefits (not features) to devs in v3? > 1) Make it faster to develop apps? > 2) Make it easier to develop apps? > 3) Make it faster to get started for new-to-Cake devs? > 4) Increase features for current Cake devs? > 5) ? > > Maybe I'm dense or not understanding the ramifications of the new > features. Reading this latest announcement, it seems like v3 just makes > changes for changes sake. You guys all love coding and it's fun to work on > the latest cool features of PHP -- I get that. You're adding lots of > "features" that take advantage of new stuff. But how much of it translates > into actual *net benefits* for current developers? > > Will an OO ORM make Cake easier to code? Faster to code? Faster to > interpret/execute? Do things that were impossible before with the non-OO > ORM? > > You mention stuff like "It's new architecture based on PHP 5.4 > capabilities will offer an easier and more powerful set of tools to build > web applications in no time." How do namespaces, traits, and closure > bindings help a dev "build web applications in no time"? > > I've been using Cake since 2008. Cake v3 feels to me like I have to > re-learn Cake from scratch due to the *huge* amount of breaking changes. It > feels like v3 is a whole new framework. > > All my current apps can't be upgraded. All the custom generic > components/behaviors/plugins I've written over the years which I use for > *all* my current/future projects will need to be re-written. All > open-source plugins will need heavy re-writes (unlike v1.x -> v2). > > Those facts totally negate the "features" of v3 for me and is pretty > demoralizing. I might as well start also considering other frameworks if > I'm being forced to scrap all my current plugin code. If the slate is > clean there is no reason for me *not* to consider other frameworks. Cake > may still end up being the best option, but with previous version changes I > didn't even bother considering the other options because of the relatively > easy migration. > > > > > -- > 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 [email protected] <javascript:_e({}, 'cvml', > 'cake-php%[email protected]');>. > To post to this group, send email to > [email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > . > Visit this group at http://groups.google.com/group/cake-php. > For more options, visit https://groups.google.com/groups/opt_out. > -- Prof. Dr. *Nilson Pena* Av. ACM, 585, sl. 1205 Salvador - Bahia 71 - 3012-3031 -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
