Topic: Proposing / Advocating for Ruby on Rails
I was wondering if anyone can give me some ideas or "talking points" about Ruby on Rails to put in a proposal for using Ruby on Rails for an upcoming project instead of our current technology cakephp.
Back in the day I was a perl guy, found RoR late last year and created a few small programs on my own. Recently I got a web developer job for a smaller company with a large online presence. At the moment and for the foreseeable future I will be the only tech person.
Our current suite of websites consists of 4 main parts. 3 are all separate smaller cakephp applications while the 4rth is a larger social networking application with over 50,000 users written in straight php. This application is scheduled to be rewritten in Sept and Oct. While I have been updating and adding to our current cakephp applications, compared to RoR, I am not impressed with cakephp at all. I find the overall implementation of things odd and confusing, while the documentation is extremely lacking. In short switching to RoR seems much more enjoyable not to mention easier and cleaner.
At the job I am the only one with any tech knowledge. No one knows what php or ruby is, so cakephp vs RoR would draw blank stares. I'm pretty sure my executive director will not have a problem with me switching technologies, but will probably want an explanation of why and what advantages will be gained. He will probably want this in a full business like proposal. This is not something I am used to writing and was wondering if anyone had any type of pointers for this kind of situation or some points I can add in for switching from cakephp to RoR