PHP…Will Work for MVC’s

So I’m studying up new ways to re-use my code (instead of having to re-write it), and quickly falling in love with the MVC (Model View Controller). It’s basically a way of developing applications that includes multiple tiers for separating the logic/rules code from the presentation code. It’s basically cleaner and more organized that way. Since my first exposure to this was Smarty for PHP ( coworkers Brent and Ellen introduced me to them, thanks!) I have kept it in the PHP family and am totally digging frameworks CakePHP and Symfony.

While I’m studying up on my .NET stuff (I’ve still got a secret love affair w/ Namespaces!), I’m tempted to explore Ruby. I went to a Ruby Hoedown a few months ago and everybody was going crazy over rules engines ruleby, communications apps built with asterisk and best practices in general.  I guess you could call me a late bloomer when it comes to making the switch. If the idea behind Ruby on Rails (the popular Ruby MVC) is to prevent bottle-necking the app with “spaghetti-code”. Why couldn’t a PHP MVC serve the same purpose? I’m not one for re-inventing the wheel. Somehow, I keep getting the idea that the Ruby programmers think that PHP programmers do the majority of their work in their Mom’s basement and write sloppy code. Again, maybe I’m just not seeing the other side of the totem pole. If Ruby is truly a more stand-alone and robust language, I probably would do well to give it a shot. Does anyone else have some experiences to share about either? I’m interested in hearing your thoughts…

bookmark bookmark bookmark bookmark

Posted by johnmaster208 on November 25th, 2008 | Filed in |


2 Responses to “PHP…Will Work for MVC’s”

  1. Leslie Says:

    Not one word of that made a lick of sense to me, but I’m totally intrigued! Keep it up John!

  2. Leslie Willard Says:

    Knock, knock, knock… is anybody there? :)

    We want more! We want more! We want more!

Leave a Comment

Error in my_thread_global_end(): 1 threads didn't exit