Comments on: Why Ruby on Rails is better then PHP http://smoothrails.com/2005/12/30/why-ruby-on-rails-is-better-then-php/ Ruby on Rails news resources and information RoR code snippets and help scripts for newbies. Mon, 06 Sep 2010 13:15:07 +0000 http://wordpress.org/?v=2.2.1 By: CAMERON http://smoothrails.com/2005/12/30/why-ruby-on-rails-is-better-then-php/#comment-904 CAMERON Thu, 24 Jun 2010 12:19:56 +0000 http://smoothrails.com/2005/12/30/why-ruby-on-rails-is-better-then-php/#comment-904 <strong>Medicamentspot.com International Legal RX Medications. Special Internet Prices (up to 40% off average US price). NO PRIOR PRESCRIPTION REQUIRED!...</strong> <a href="http://medicamentspot.com/products/antiviral/combivir/order/ Combivir@buy.online" rel="nofollow">.</a>... Medicamentspot.com International Legal RX Medications. Special Internet Prices (up to 40% off average US price). NO PRIOR PRESCRIPTION REQUIRED!…

Combivir@buy.online” rel=”nofollow”>.…

]]> By: Shad http://smoothrails.com/2005/12/30/why-ruby-on-rails-is-better-then-php/#comment-835 Shad Sun, 02 Nov 2008 01:00:06 +0000 http://smoothrails.com/2005/12/30/why-ruby-on-rails-is-better-then-php/#comment-835 We're back to php 5 and mysql 5 as of November 2007. Ruby on Rails proved too server intensive for many small applications. In addition - it's really catered to a developer environment - not very web designer/webmaster friendly. Designer should never have to touch the command line in my opinion to make basic changes to files. In the end, we stopped using Ruby on Rails because it occupied more server resources, required advanced server configuration (in many cases), required more testing after simple pushes, not web designer friendly and seems to be loosing main stream support. We’re back to php 5 and mysql 5 as of November 2007. Ruby on Rails proved too server intensive for many small applications. In addition - it’s really catered to a developer environment - not very web designer/webmaster friendly. Designer should never have to touch the command line in my opinion to make basic changes to files. In the end, we stopped using Ruby on Rails because it occupied more server resources, required advanced server configuration (in many cases), required more testing after simple pushes, not web designer friendly and seems to be loosing main stream support.

]]>