In article <1121441618.529649.252080@g14g2000cwa.googlegroups.com>,
Zach Dennis wrote:
> The only thing that will stop Ruby from growing is if people don't use
> ruby. If you use ruby, that is a +1 chance that Ruby will be used at a
> company; small, medium, large or huge later this year.
Very true. For larger companies there are typically some PHB's that
look at the current popular technology trends and hop on those
bandwagons. "Let's see...what's the other guy using? Well, if it's good
enough for them we can certainly use it!"
Do remember that some of those conservative voices are not PHBs.
Ofttimes, they are people who have heard this before, many times, and
have had unpleasant surprises. If you are going to try to sell Ruby, or
Java, or anything, you have to know how the sold-to thinks.
I am a very good Java programmer, and have done Hibernate, Cayenne, JSP,
Servlets, WebObjects, and a bunch of other stuff. Every technology I
have seen in the web app space has had testimonials that were frankly
identical to the testimonials for RoR. I was suspicious.
When James Duncan Davidson mentioned how successful Ruby on Rails has
been, I gave it another look. I have found that my conclusions often
agree with his, and he is very bright and very experienced in many of
the same spaces I am, so if he thinks Ruby is good, it has a good shot
at solving my problems too.
I have not tried Ruby for a serious project, but it looks good from the
small toy projects I have tried.
Would I suggest it for my bread and butter clients for a mission
critical app? Not at my current level of understanding. Would I
suggest it for a testbed or POC? Definitely - we would then know how
well Ruby worked with _our_ systems and _our_ needs. That is how MacOS
X got into our toolset some years back, and how MySql got so popular for
us, and why we built a linux cluster with a few hundred boxes in it
almost a decade ago - they all worked well in the test projects, and we
felt it worth the risk to try something new in return for the benefits
the new thing offered.
In answer to the original question - Ruby is not going to lead to as
many jobs as Java right now. It is still probably worth learning, and
using, as you will then know, not guess, but know where it fits in your
toolbox. When someone interviews you for that next job, which might be
a Java or a .NET, or whatever, job, you can bring up Ruby and
intelligently state the costs, the benefits, the risks, and whether
_you_ think it is a good idea.
If the project fits the Ruby strengths, then it just might be the right
tool.
Scott
···
"gregarican" <greg.kujawa@gmail.com> wrote:
--
Scott Ellsworth
scott@alodar.nospam.com
Java and database consulting for the life sciences