Topic: I want to convince my bosses that Ruby > PHP
.... boy, that title begs for flame bait, but I am getting desperate.
I am monstrously confused by my (potential) employers adherence that the ecommerce infrastructure MUST be powered by PHP and an "out of the box" solution . . . while maintaining to me . . . their potential developer . . . that having a robust architecture and API are vital.
Their reasoning? "All ecommerce solutions are written in PHP" (keep in mind, these guys are business majors . . . not techies)
Now, I am not going to lie, I am terribly biased. I spent about 5 minutes in PHP before giving up the ghost and moving to greener pastures ... I fell in love with Ruby and her friend Rails and have spent the past 18 months in development bliss. Ruby is expressive and Rails "just makes sense" to me . . . problem is . . . I don't have the experience in both worlds to make a substantive argument on why I want to develop our platform in Ruby and Rails. What I have been attempting to do, instead, is pick up PHP (for syntax, I haven't tackled any of the frameworks yet) . . . but I want to know:
Are there any resources out there I could read up on for business arguments on Ruby vs PHP? How can I tell these guys "These are the reasons you want it in Ruby and Rails . . . these are the advantages over PHP and it's frameworks".
I don't mean to begin a debate or anything . . . but am more looking for resources and articles if they exist. google brought up a few things, but most of them were pretty old (2006). Anyone have any ideas?