From: Seth Rasmussen Date: 2006-03-23T04:11:36+09:00 Subject: Re: Rails vs. Ruby Evolution On 3/22/06, stu wrote: > It would be nice to see them do Object#ROR_to_json so its know what is > really 'core' and what is a rails thing, prefix things with ROR or > something. > > I dont want to know rails, and have no plan to use rails, and I > shouldnt need to know rails to know ruby as seth implies further down > in the thread. No, I don't. Please read more carefully. Regarding uneasiness and dependency issues... if you're not going to DIY, how much room do you have to complain? Well, of course we can all complain all day, but... what are you going to do with that? If you're going to depend on the work of others, you should expect some restrictions on your ideals. It's just what I sense as this sort of Chicken Little, obsessive control type of worrying that seems unwarranted. If the community wants to take some stuff from Rails and put it in core, then great, let's do it. If you want an ActiveRecord that doesn't depend on other libraries, then write it. Etc. Many are so worried about Rails somehow ruining Ruby when, for my money, I'm just happy and excited that such tools exist. You can always take core Ruby, WHATEVER that is, and make it WHATEVER you want. You can always rewrite a better Rails. You can always write a Rails-killer. What more do you want? -- Seth Thomas Rasmussen http://sethrasmussen.com/