I thought that I’m basically just an annoyed n00b and that the community at large accepted these changes. Now I’m wondering if Rails 2 created some sort of schism, fracturing the Rails community in two.

Are there enough people hating the new Rails to fork the code and back port the good features from Rails 2 without breaking the old behaviors?

Now, after a week of struggling with Rails 2, I’ve discovered that I can’t reuse any of my code. Adding additional def’s to the scaffolding and adding new views simply doesn’t work.

Many of the important plugins don’t work either. For example, the logingenerator worked and could be easily modified to include permissions.

The lack of backward compatibility is a slap in the face to those of us who have spent so much time developing the code that enabled the databases to do amazing things.

spot on! - i am one of those ‘rails newbies’, who’s been methodically working through the sitepoint book, only to run into this fucking brickwall after 140 pages.

I have to say, I couldn’t have said it any better. What were they thinking?!

(I support obama, too.)

i’m beginning to think the ‘easy’ adjective, generally applied to learning rails is some kind of twisted joke.

I was very disappointed to see scaffold removed and replaced with a “generate scaffold” command which adds like 100 files right off the bat.

For a web framework that “makes web development easy”, they sure did a good job of frustrating lots of future Rails developers who are just starting.

I would really like to see scaffold added back to official release, but if it hasn’t happened yet then I doubt it will.

Jason