> However, when developing the app I chose to rely more on Alan Bradburne's
> "Practical Rails Social Networking Sites". The reason for that is that in my
> opinion, Alan's way of developing the app was 1) more modular (every
> iteration / chapter is a self-contained web app in itself); 2) more
> REST-based.
Thanks for the comments. The goals of RailsSpace and Alan Bradburne's
book were quite different, and it was our fault for not making the
difference clearer. RailsSpace was designed as a general tutorial for
beginning Rails programmers, whereas Alan's book was aimed
specifically at building social networks and assumed that readers
already knew Rails. When building a specific kind of app (and when you
can assume prior Rails knowledge), modularity makes more sense; for a
tutorial aimed at beginners, an integrated narrative structure is more
effective.
As for REST, when we started RailsSpace there wasn't even REST support
in Rails! Indeed, it was terribly frustrating to have RailsSpace come
out just in time to be swept away by the REST revolution. Nowadays, of
course, REST is standard, so the Ruby on Rails Tutorial book will
definitely use the REST architecture where appropriate (which is
basically every chapter after chapter 4).