1. Ruby 2. Rails If you try to learn Rails at the same time that you learn Ruby you'll inevitably get to a point where you have no idea about what's going on. The person that wrote Rails is a Ruby expert and it shows, which means that sometimes you will have no idea about the techniques being used and how things work. This is true even if you have a decent understanding about Ruby (I raise my hand there). However, if you learn Ruby (and practice it before starting writing code for/with Rails) you'll be in a much better position when you start using Rails.
Pepe On Dec 11, 6:51 pm, Ryan Bigg <[email protected]> wrote: > If I had to learn rails again I would learn ruby first then drift over > into rails because I think that would give you a better understanding > of how ruby works > > On 12/12/2008, at 5:55, olivierntk <[email protected]> wrote: > > > > > I started rails by reading Beginning Rails from Apress. > > > It will take you through most of what you need to know to start Rails. > > Being a .NET developer, it was quite easy to pick it up but I believe > > it is accessible to non web developer. > > > With Rails, you don't need to learn SQL (unless you have very specific > > tasks to achieve). > > JavaScript is nice to have (I would recommend you to use jQuery, a > > JavaScript framework) but you can have a full web app running without > > JavaScript. > > Apache? No need, Rails comes with Mongrel. > > > Ruby ... of course but you'll just need the basics and learn as you > > go. > > > My 2 cents --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
