InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Rails 2.0 - What's a Newbie to Do?

Posted by Rick DeNatale on Dec 27, 2007

Sections
Development,
Architecture & Design
Topics
Ruby ,
Ruby on Rails ,
Programming
Tags
Rails Plugins ,
Documentation ,
Ruby on Rails
With the recent release of Rails 2.0.0, 2.0.1, and now 2.0.2 in rapid succession, the Rails support discussion groups have had frequent inquiries from newcomers to Rails who are having problems following popular tutorials such as the books "Agile Web Development with Rails" by Dave Thomas and David Heinemeier Hansson. The Thomas/Hansson book, which is commonly referred to as AWDR is already in it's second edition which is just about a year old and covers Rails 1.2.

While the difference between Rails 2.0 and its predecessor Rails 1.2 are far less drastic than those between Rails 1.2 and Rails 1.1, enough potholes are there to trip up the unsuspecting newbie.

One of the themes of Rails 2.0 was to make it leaner. This means that some features which were previously standard have been removed from the core and relegated to plugins. For someone following a tutorial based on an 1.2, this can be a stumbling block. Two examples:
  1.  Many tutorials are base on using MySql as the database adapter because it has always been the Rails 'default.' Up to now, that is, Rails 2.0.3 changed the default to Sqlite3. AWDR describes how to use Sqlite3, later in the book, but a newbie following along might not be equipped to troubleshoot the problem without help at the time it's encountered.
  2. The early parts of AWDR make use of the dynamic scaffolding feature of Rails which now is only available after the scaffolding plugin has been installed with:
              script/plugin install scaffolding 
    Other such "missing" features in Rails 2.0 include AJAX in-place-editing and auto-completion, and some of the popular acts_as_x model extensions. Someone following an aging tutorial might try running the command:
              script/plugin list 
    to see if one of the available plugins looks like it might provide a missing feature.
Another option is to use Rails 1.2.6, work through the tutorial(s) and then consider moving to 2.0. First, install the 1.2.6 version of Rails:
    gem install rails --version 1.2.6 
Then, either remove any rails 2.0.x gems you have installed, or specify the version on the rails command when you generate your project:
    rails _1.2.6_ my_rails_project 
Most commands installed by gems are wrappers which invoke the code in the gem, and allow you to specify the version of the gem used by calling them with a version number surrounded by underscores as the first argument.

There are already some books which cover Rails 2.0 available such as "The Rails Way" by Obie Fernandez, but so far they all seem to be targeted as resources for those with a little more Rails experience under the belt. Some of the "Classic" Rails literature will no doubt be updated as time goes on, and newer tutorials will join them.

In the meantime the Rails newbie has the choice of either struggling through the changes as they are encountered, or perhaps more wisely using the version of Rails which matches the tutorial until a certain level of mastery has been achieved.
Misinformations? by Kristof Jozsa Posted
Re: Misinformations? by Matt Henry Posted
In correct book title by Nicholas Henry Posted
Some inaccuracies by Chu Yeow Cheah Posted
openrorbook = (german) Rails 2.0 Book also for beginners by der kaan Posted
Rails 2.0 Screencast and Tutorial by Fabio Akita Posted
Peepcode Screencasts by Matt Henry Posted
  1. Back to top

    Misinformations?

    by Kristof Jozsa

    I haven't read it myself, but all the reviews seem to claim Obie Fernandez's book as a throughout one aimed towards beginners. On the other hand, it has been confirmed several times through the 2.0 release cycle since the beta series that the AWDR book will NOT get an update for Rails 2.0.x. I might be wrong in both cases so someone please correct me, as I'd also like to know these for sure!

  2. Back to top

    In correct book title

    by Nicholas Henry

    You mention the book "Active Web Development with Rails" - the title of this book in incorrect. The correct title is "Agile Web Development with Rails".

  3. Back to top

    Some inaccuracies

    by Chu Yeow Cheah

    Just wanted to point out some inaccuracies in the article. The new default database of SQLite3 was actually introduced in 2.0.2 (2.0.3 is not out yet). It may have been a bad move publicity-wise but you can simply do 'rails -d mysql myapp' to generate a Rails app pre-configured for MySQL as detailed in weblog.rubyonrails.org/2007/12/17/rails-2-0-2-s....

    Also, dynamic scaffolding is completely deprecated/removed - even installing the plugin you mention will still cause failures in using dynamic scaffolds. Mind you, normal scaffolding still works, just not _dynamic_ scaffolding.

  4. Back to top

    openrorbook = (german) Rails 2.0 Book also for beginners

    by der kaan

    OpenRoRBook is a free German language book that covers Rails 2.0 development. It's availabe on www.rubyonrails.de/newsitems/98. We hope to find someone who have time and fun to translate the book into English in the future.

  5. Back to top

    Rails 2.0 Screencast and Tutorial

    by Fabio Akita

    I think these can help as well:

  6. Back to top

    Peepcode Screencasts

    by Matt Henry

    The Akita on Rails screencasts are great. Rails newbies might also check out Geoff Grossenbach's intro screencasts at Peepcode. They come with notes that point out the spots where Rails 2.0 differs from 1.2. Very handy for those just starting out.

  7. Back to top

    Re: Misinformations?

    by Matt Henry

    The Obie Fernandez book is awesome, but he's careful to say in the preface that it's not really intended for beginners. Most of the reviews I've seen say the same.

Educational Content

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.