4 ms·
Wow, this guy really hates CakePHP. If you know what you're doing and don't just presume Cake has done it for you, none of those problems should exist.
by Jleagle 13y ago
Wow, this guy really hates CakePHP. If you know what you're doing and don't just presume Cake has done it for you, none of those problems should exist.
- TheCapn 13y agoI find that to be very true. Seems a lot of amateur programmers pick up CakePHP for one reason or another without actually knowing PHP and try to drive every screw with the one hammer they have. When everything's suddenly broken they blame the hammer. EDIT: Although I suppose the author's point of view is from the outside-in where he's tasked with cleaning up the mess that amateurs leave behind and has a bias against it.
- Schlaefer 13y agoIf you know what you're doing you will not pass around huge arrays (in PHP) by value. Or pass them around (in CakePHP) at all, it's maybe a MVC warning flag that you do something in a place you shouldn't. Related note: CakePHP 3.0 (current is 2.x) will use objects [1]. [1] https://groups.google.com/d/msg/cake-php/-TLn6RpHt4U/EAP0lt2yjsAJ https://groups.google.com/d/msg/cake-php/-TLn6RpHt4U/EAP0lt2...
- smacktoward 13y agoI have no brief for or against Cake (never used it myself), but input filtering seems like exactly the sort of tedious-but-necessary infrastructure code that a good framework is supposed to let you avoid having to write from scratch for each new project. If Cake doesn't do that, I don't think it's unreasonable to count that as a strike against it.