On Thu, May 28, 2009 at 2:05 PM, dave p <noone / nowhere.com> wrote:
> I am relatively new to Ruby and Rails, but have a lot of experience with
> Perl and PHP.  ¨Âæôåò ìïïëéîáô Òáéìó¬ òåáììù ìéëå Òõâùâõæéîä Òáéì> to be to restrictive in the way you have to do things.
> This article:
>
> http://www.oreillynet.com/ruby/
> blog/2007/09/7_reasons_i_switched_back_to_p_1.html
>
> sort explains how I feel, mostly #5.  ¨Âáùâå êõóô îååä ôï óðåîíïòå
> time learning Rails.
>
> Moving from Perl to PHP was really easy.  ¨ÂÈÐ óååíôï âå Ðåòì íïäéæéåä
> for the web.  ¨Âèááí ôèéîëéîç ïæ ÷ïõìâå ÐÈíïäåìåïî Òõâù ôè> way PHP is modeled on Perl.  ¨Âáùâå ãáìì éô ÒÈЮ
>
> Thoughts?
>
>

Rails is not restrictive but it is very opinionated. There is a difference.
You can get Rails to work around your data your way but then you'd be
better off writing your app with a different framework or directly on
top of Rack (similar to how you would with PHP)
Bottom line, Rails is not the only way to do web development with Ruby.

PS. Ruby has a good number of perlisms of it's own

Andrew Timberlake
http://ramblingsonrails.com

http://MyMvelope.com - The SIMPLE way to manage your savings