the logic behind it is, if you encounter a problem while using rails 3, your past rails knowledge will not save you and you will spent more time while searching answers than developing your application, but if your ruby background is good, than you can easily solve the problems you'll encounter.
On Aug 23, 10:45 pm, Colin Law <[email protected]> wrote: > On 23 August 2010 19:31, gkaykck <[email protected]> wrote: > > > if you know RUBY very well, not rails, than there is no problem, go > > for rails 3. > > but if the reverse is true, if you know RAILS well not ruby, which > > most of people do, then stick with 2.3.8 > > Can you explain the logic of that please? > > Colin > > > > > On Aug 23, 5:55 pm, Dani Dani <[email protected]> wrote: > >> Hi, > >> If I'm going to start developing a new rails based web application, > >> should I go for Rails 3 or Rails 2.3.8 ? why this and not the other ? > >> Thank you. > >> Dani > >> -- > >> Posted viahttp://www.ruby-forum.com/. > > > -- > > 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 > > athttp://groups.google.com/group/rubyonrails-talk?hl=en. -- 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.
