From: Seth Rasmussen Date: 2006-03-23T06:31:38+09:00 Subject: Re: Rails vs. Ruby Evolution Hi stu, On 3/22/06, stu wrote: > In reply to seth; > > well your quote > > >I think a healthy dose of familiarity with both should > > foil that potential "crisis." > > implies that one should know both in order to know Ruby... No, it doesn't. It implies that if one is worried about confusing Ruby for Rails or vice versa, that simply knowing which is which will avoid that. > I have no doubt Rails is a good thing at all, but I dont think Rails > should drive the direction of a generic programming language. I know not every piece of opinion begs comment, but it seems interesting that you seem to be responding to things which have not been stated or implied. This all started by somebody simply saying, basically, "Hey Rails has a bunch of nice core extensions... maybe some of them should be in the Ruby core?" That says nothing about Rails driving anything but its own success and some other people going, "hey, that's not too shabby." > I want to > see more adoption of Ruby and Rails is driving that, I just dont want > to see Rails dictate what goes into Ruby. It's going to be okay... it's going to be okay... > How many rails programmers will expect 'to_json' to be standard Ruby > since its bound to Object? (i guess, I am making the gross assumption > that there are more Rails programmers than Ruby programmers, making the > disction between rails only programmers and those that do rails and > ruby)... I dunno, who cares? Are you like those fools? No? Great. The world spins on.. -- Seth Thomas Rasmussen http://sethrasmussen.com/