Throughout my years of PHP development, both in environments where I’m only acting as a developer because the staff was all laid off and I, as graphic artist, obviously had the know-how to start coding (just ask me about 2001), or as a genuine developer (more recently). It seems to be assumed that if you ask a PHP developer about his growth as a developer, he will mention first doing procedural code, then moving to function-based code, then OOP(object oriented programming), and finally landing at the stage where frameworks are designed & code takes on an elegant, almost mystical aura.
Well, I’ll just say it. Put it out there. Let it stand on its own merits.
_I don’t like MVC architecture in PHP, and will strenuously oppose developing in that environment._
I’ve toyed around with countless frameworks already developed (Symfony, Qcodo, Cake, &c) and I just don’t like it. Though limited in scope, the work I’ve done in Ruby on Rails has taught me the joys of the framework, and I can appreciate the beauty and stark cleanliness of the code: but PHP is not Rails.
That should be my new slogan. People on the PHP board seem to really, really, really want to make it into Rails, and I just don’t get it. The same people spend most of their free time talking about how terrible Ruby is. I can’t wrap my head around it.
So that’s it. Just me talking about how I’d rather write classes & do method calls all day than wrap myself into the taffeta and lace of the MVC structure.
Comment (1)
Well said. PHP has one very big problem that limits its scope (no pun intended): namespaces. Why are there over 30 functions in global scope beginning with the letter “a”? I have since moved on to Python/Django since I literally reached the end of the PHP OO road. Have you looked at Django? Oh, and perhaps you remember me from that group of laid off developers ;)