Greg said:
For example: although some would push Ruby for big projects there are
reasons to be circumspect about such a decision. Not being a Ruby expert I
cannot elaborate too much, except to say that there are some
industrial-strength-unfriendly-and-too-powerful-perhaps features in the
language, like C++ but much more elegant possibilities for self destruction.
When I started out with Ruby, I had the same suspicions. Open classes,
no type declarations on method headers, require
'filename_instead_of_class_name', among others, scared me about using it
as part of a team. I did my best to investigate this to see if it rang
true -- my conclusion now is that Ruby is not a good idea if nobody has
any control over the team, and it's complete chaos. There are enough
harmful things that can be done, but are harder to do in whatever your
team already uses (if only because they know the language), that you
need a team to actually coordinate, and write unit tests, and rdoc
comments, and agree on certain standards, and review each other's code,
etc. But if you have that, it seems to me that Ruby would make the team
go much faster.
The Rails project also needs proper examination. It seem like the soloution
to all our problems, the way people talk about it. But there are sounds from
the deep (the WWW) to think that it is not the solution to all our
problems. Again I am unable to elaborate, but you can look around.
I can elaborate a little bit. The "sounds from the deep" mostly point to
a lack of JMS, JTA, an ESB. Instead, Rails & Ruby have different
solutions to asynchronous messaging, transactions, and distributed
processing -- and they may not be overly complex enough for your needs.
If you've got requirements for that sort of stuff, then...
So be careful of the ruby fanatics; they have funny starring eyes and froth
coming from their mouths, like mad dogs.
Actually, we're pretty reasonable.
And yes, I'll throw in a "Ruby is fantastic for prototyping, and then
realizing that your prototype is actually a fully-functional version of
the thing you were trying to mock up." But that took me, like, 2 days
to discover.
Devin "Mad Dog" Mullins