Brian Moon recently wrote a post for his blog titled
PHP Frameworks. The post is based on presentations and conversations at The PHP Community Conference. Unlike some that just bash on them though, or some that propose “no framework” development, Brian suggest that PHP itself is a framework.
In my session, I talked about the history of Phorum. One of the things I covered was the early days of PHP. Back in the 90s, before PHP, most dynamic web work was done in C or Perl. At that time, in those worlds, you had to do all the HTTP work yourself. If you wanted a content type of text/html, you had to set it, in code, on every single response. Errors in CGI scripts would often result in Apache internal error pages and made debugging very hard. All HTML work had to be done by writing to output. There was no embedding code with HTML even as a templating language. PHP changed all that. You had a default content type of text/html. You had automatic handling of request variables. Cookies were easily ingested and output. You could template your HTML with script instead of having to write everything out via print or stdout. It was amazing. Who could ask for more?
Brian goes on to make several other good points but you are going to have to actually visit his blog to read them. If you are a Framework-Fanboi, you won’t be insulted by this post, however you may be challenged. If you’ve never worked with a framework, this post will give you some insights to think about.
Head on over to Brian’s blog and invest 5 minutes. I promise you, it will give you food for thought for much longer than that.