| Flinn Mueller on 19 Sep 2007 03:55:53 -0000 |
|
I find that PHP users don't understand Rails because much of it depends on understanding the Active Record design pattern, ORM and object persistence. Some of you know I recently took a position as a PHP developer ( I hate even saying that). As a Rubyist for the last 2 years I've been running into some issues trying to apply Railsish concepts (aka best practices) in a PHP environment. I find that since PHP isn't purely object oriented there is a tendency to use classes just to group like-functions. Also rather than passing around objects there's a tendency to pass primitives using classes only to scope methods to a particular domain... $bar = Frob::nicate($foo); or worse yet $frob = Frob($db_object); $bar = $frob->nicate($foo); So the question I find myself consistently running into is, if you are using PHP and you find the value in using ActiveRecord why try to break your back forcing PHP to do something it can't? Just use Ruby. If you don't see any value in the pattern or how it's implemented in Ruby, then go on using PHP, see you again soon ;-) On 9/18/07,
Mat Schaffer <schapht@gmail.com> wrote:
Also, I got a note from the PHP Meetup group awhile back asking about _______________________________________________ To unsubscribe or change your settings, visit: http://lists.phillyonrails.org/mailman/listinfo/talk
|
|