A An insightful post by the King of php himself can be found here: THE NO FRAMEWORK PHP MVC FRAMEWORK. Confusing? hahah – well Andy Jeffries ( A PHP, RUBY ON RAILS AND MYSQL Developer) sums it up really well here: DESIGN PATTERNS VS AGILE DEVELOPMENT
I posted this in a forum in the morning today, please read the reply i got:
Keep an open mind …….
A good framework:
1. better separates presentation from logic
2. has a clear documented structure
3. has featuresHe uses a view, controller, and model but he doesn’t use a “front controller”. URL’s are mapped directly to views. That’s not necessarily bad, (that’s the asp.net way) but:
- without a messy .htaccess file, you miss out on nice flexible hackable urls
- you miss out on pre processing like showing a cached page without loading the entire view file and all it’s includes.
I believe this person who commented on my post in the forums has a POINT WORTH NOTING…
{ 1 comment… read it below or add one }
Really good information