From: khaines@...
Date: 2007-03-28T10:26:30+09:00
Subject: Re: On Enterprise Ruby

On Wed, 28 Mar 2007, S. Robert James wrote:

> 2. Immaturity of Libraries. How many of the libraries that your
> project depends on have version numbers < 1.0?  'Nuff said.

So, we'll all just add 1.0 to existing version numbers, and then the 
libraries will be mature.

> 3. Clever code.  Kent Beck says that when he uses a clever trick, he
> feels bad, that's he wasn't capable of using a simple, well known
> solution.  Yet I see a lot of Rubyists - esp. Railers - who seem to
> get a kick from programatically redefining a class or using
> method_missing to avoid a comma somewhere.  Come back to that 3 years
> later, and good luck.

Eh.  There's a HUGE difference between leveraging language features such 
as open classes versus being clever just for the sake of being clever, and 
Ruby certainly doesn't have a corner on that market, either.

> 4. Arrogance.  All those "databases are stupid, referential integrity
> is for wimps, and CIOs should be fired" posts.  Yuck!  To me, the
> rampant arrogance, combined with immaturity, is the greatest long term
> risk to the health of Rails.  Luckily, there's been a lot of

And, fortunately, there's a lot more to Ruby than the Rails world, too.


Kirk Haines