« Return to Thread: Is the rails 2.0 scaffold system philosophically ( not technically? ) broken?

Re: Is the rails 2.0 scaffold system philosophically ( not t

by Brian Hogan :: Rate this Message:

Reply to Author | View in Thread

Thanks David - you and I are in complete agreement. I didn't mean to state that I explicitly use Rails 1.x... I just use Rails 1.x *concepts* like classic routing, non-REST controllers, etc when we're starting out.

On Mon, Mar 3, 2008 at 9:42 AM, David A. Black <dblack@...> wrote:
Hi --

On Mon, 3 Mar 2008, dankelley wrote:

>
> On Mar 3, 10:47 am, "Brian Hogan" <bpho...@...> wrote:
>>  it's much easier
>> to start them on Rails 1.x and move to Rails 2.0 and REST later.
>
> This suggestion worries me a little, because I have found that the
> conversion is not simple.
>
> If version 2.0 is compellingly superior to 1.x, then newbies should
> start there.  (Using the latest stable version is a long-standing
> tradition in software, because it is effective.)  Nothing in this long
> and useful discussion thread suggests that the RoR developers are
> inclined to add the feature that is being discussed to an upcoming
> version.  And so there is a simple choice: use RoR 2.0 as it is, or
> choose another framework.  (This second option is not meant to be
> heretical; newbies should be aware that there are alternatives.)

Keep in mind, though, that Rails 2.0 is in this respects a superset of
1.x. You don't have to use the RESTful facilities if you don't want to
(and you certainly don't have to use the scaffolding). I would agree
with Brian in spirit but I'd put it slightly differently: it's easier
to start with the non-REST stuff and then learn the REST stuff, but
all of this can be done in the context of 2.0, i.e., it's not
specifically a 1.x vs. 2.0 thing.

In training people in Rails, I definitely do not start with REST and
resources. map.resources is essentially a macro that creates a bunch
of named routes for you -- so if you don't know what a named route is,
you can only do it in a black-box and parrot-like way. Learning named
routes doesn't make much sense until you understand routes, and routes
don't make sense until you know the basics of the request cycle... and
so forth. So I would never introduce someone to Rails by telling them
to write map.resources in routes.rb and trying to proceed from there.


David

--
Upcoming Rails training from David A. Black and Ruby Power and Light:
  ADVANCING WITH RAILS, April 14-17 2008, New York City
  CORE RAILS, June 24-27 2008, London (Skills Matter)
See http://www.rubypal.com for details. Berlin dates coming soon!
--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk@...
To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---