It's interesting that the OP here is cynical about "marketing" efforts
from DHH, but not from Sun and Microsoft, i.e. Java, C# and all tools
built around them.
Regards,
Dan
···
-----Original Message-----
From: David Heinemeier Hansson [mailto:david.heinemeier@gmail.com]
Sent: Monday, July 18, 2005 8:44 AM
To: ruby-talk ML
Subject: Re: Ruby momentum?
> I'd have to say that all the "RoR 10x faster than Java"
articles are
> really giving rails a bit of a bad name. Around here, RoR
is somewhat
> of a joke, just because of all these claims of whiter teeth, bigger
> smiles, cleaner floors, etc, that Rails will bring. It
just makes the
> whole framework seem like an enourmous marketing effort,
which to many
> technical people indicates a lack of quality. I'm sure that if we
> gave Rails a try here, it would be quickly accepted, but breaking
> through the cynicism is really hard when a product is being
so heavily
> hyped.
There's no doubt that breaking through the awareness barrier
leaves a residue of backlash with some. I wrote about this
subject and some of the ecosystem numbers at http://www.loudthinking.com/arc/000484.html
--
David Heinemeier Hansson
It's interesting that the OP here is cynical about "marketing" efforts
from DHH, but not from Sun and Microsoft, i.e. Java, C# and all tools
built around them.
Assuming I'm the OP, I just don't see how that belongs on this list.
This is a Ruby list, where I discuss Ruby issues. I'm not on any Java
or C# lists, because I don't care about those "technologies." They
aren't interesting to me, and I don't use them. I have a personal
distaste for Java, mostly due to the fact that it feels to me like a
neutered version of C++ (which I like), but my Java opinion has no
place on this list.
I would definitely like to see some comparisons where Rails is
compared to the big industry strength tools out there, and I'd really
like to see something where most of the features of both (or all)
toolkits are mentioned, even when the features are unique and not
matched. It's good to be able to see holes in a toolkit when deciding
what to use.