On 10/21/13 7:56 AM, Curtis Maurand wrote:
I've been doing some research on frameworks, etc. Everyone has one they like and even the development environments that you can get have their favorites and books seem to have their favorites. I've been looking at Cake, Symfony, Zend, PEAR-Flexy, Smarty, Joomla, etc., etc., etc. I'm not going to ask which framework everyone likes best because that's pointless. All of the web hosting control panels/billing systems do not support the technologies that I'm currently using (dbmail, powerdns). To that end, I need to write my own. Should I be using a framework at all?
You will use a framework. That will happen no matter what, because if it doesn't it means you're writing nothing but one-off code, which means your app is going to be crap. Exceptions to this rule are when the entire code base is under ~2000 lines, aka "is not actually interesting".
The question is whether to build/evolve your own framework or to use one "off-the-shelf".
If you want to learn then write your own, study another one, rewrite your own, study another, rewrite your own again.
If you want to just get the damned job done, use one off-the-shelf. There are varying degrees of off-the-shelf-ness depending on which framework you use (and some, like Symfony, offer multiple levels all on their own), and depending on your situation you may want something more or less pre-built and opinionated. (I'm partial to the Symfony family, for obvious reasons, as it offers many granular layers of opinionatedness, but there are lots of other viable options.)
But really, you've got better things to do than to write yet another routing system. Leverage packages off of Packagist.org via Composer if at all possible.
If you need more convincing, I will cite Fred Brooks: http://www.cs.nott.ac.uk/~cah/G51ISS/Documents/NoSilverBullet.html --Larry Garfield -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
