From: S2 <x@...>
Date: 2008-07-05T04:37:40+09:00
Subject: Re: from ruby/RoR to Java (framework unknown) :(

James Britt wrote:

> You need to be able to explain to them just why you get "goose-flesh".

Well yes. That part is in the past. Our small RoR group already explained
that.
 
> No doubt everyone on this list is automatically sympathetic to your
> plight, but truth is that much of what we see as obvious about Ruby is
> not so for others.

Sure.

> I don't see how anyone can expect people to just be instantly
> enlightened about the value of using Ruby; folks need facts.*

Of course.

> If Ruby (with Rails or whatever) is the objectively better choice then
> you should be able to demonstrate that.  There has to be something
> tangible, something other than "I like it."

I can't agree more. But as I sad to phlip, it's not a "technical" argument I
have to fight this time. Who made the decision knows RoR is qucker, faster,
better solution to almost all our development needs. I quote myself:
what we use has not necessarily be the best tool for the
job, but it should be the same for everyone, so people can be moved from
one project to an other without switching from one Framework/language to
another.
I have no arguments against that.
Maybe they are right. It's ok to switch to Java. But at that point I will
feel castrated, wasting time on config files and generating getters and
setters with eclipse, waiting for tomcat to restart to see the changes on
my code and sending war files to the sysadmin for deploy instead of a
convenient svn update.