Since s.ross talked about deployment differences I'll skip over them here.
If you are just talking about writing a PHP app from scratch as opposed to using Ruby (the language) with Rails (the framework) then there is NO advantage to using PHP. Rails gives you so much help with the little annoyances that you no longer have to worry about the little things and can concentrate on the big things. Now, if you prefer coding in PHP there are frameworks out there such as CakePHP and CodeIgniter that are open-source MVC frameworks for PHP that work similarly to RoR. I was a PHP coder long before I switched to RoR and have tried both of those frameworks. They are pretty good, but I didn't *get it* with those frameworks like I did with Rails. IMHO Rails makes much more sense, as in 'common sense.' I find that I don't have to look up as much in documentation because my first 'guess' as to what a function is called, what the syntax of a particular feature is, etc. is usually correct. However, it's all personal preference so I would suggest trying out as many different frameworks as you can and decide which one is best. If you have any python experience try Django, if you are a Microsoftie try ASP.NET MVC, and try out the PHP frameworks I mentioned. Decide what you are most comfortable with. On Jun 9, 3:01 am, "s.ross" <[email protected]> wrote: > On Jun 8, 2009, at 11:37 PM, Zayd Connor wrote: > > > Why are there more web design users using PHP instead of using > > Rails? Is > > there an advantage using PHP over Rails? > > > Thanks > > I'll restate the obligatory: PHP is a language; Ruby is a language; > Rails is a Web App framework. So... > > Up until recently, the deployment story for PHP was stupid-simple > because it was on almost every shared Web host running in mod_php and > you could sign up and have "Hello World" serving up Web pages in 5 > minutes. PHP is (debateably) a bit more Windows-friendly as well. > CPanel on the shared hosts set up .conf files for Apache that made > everything work nicely for a PHP app and you really didn't need to > know what was going on under the hood. > > Rails started out with a bleak deployment story, but quickly > Switchtower, renamed Capistrano changed that. But ever-changing > recommended "Rails stack" has made deploying much more of a decision- > making process than pushing out a PHP app. Things were beginning to > settle down with all the cool kids setting up nginx servers proxying > to mongrel (or thin or evented-mongrel) clusters and along came > Phusion Passenger. That's mod_ruby. Now Rails deployment is stupid- > simple. > > But in either case, you really *do* need to know something about > what's going on under the hood. If you're doing anything that matters, > you'll want to get it right. Repeatably right. Testably right. Not so > easy for Rails, even harder for PHP. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
