From: Robert Klemme <bob.news@...>
Date: 2004-10-26T20:39:04+09:00
Subject: Re: Server Programming


"Andy Stone" <xsltguru@gmail.com> schrieb im Newsbeitrag
news:569c94e504102520022fb91850@mail.gmail.com...
> I agree.  In relation to a process, the overall speed can be affected
> by many factors including code design, database design and... I could
> go on, but I'm sure you already know all of this.
>
> If there was a  choice, I would trade some speed for reliability any
> day.  What good is a super fast process if it crashes from time to
> time?
>
> I heard that comment a lot about writing code faster with Ruby.  Which
> is one of the main reasons I am evaluating Ruby.  As the sole
> developer at the day job, maintaining two entirely different and in
> some areas, complex web sites along with the intranet, this aspect of
> Ruby could help me out tremendously.

OTOH you have to write the code from scratch, i.e. you have increased
effort upfront.  That may or may not be acceptable in your case.  From
what I've read in this thread I'd have a slight tendency to stick with the
Java version, get me a copy of Eclipse (if you don't have it already) and
start a refactoring frenzy to get the code into better shape.  It might
well be that the occasional hang is due to some threading problem which
came into existence through improper use of synchronization.  *If* you go
down that road "Concurrent Programming in Java" (Doug Lea) is an excellent
reference.  (It's also good as a general introduction of MT issues
though.)

Kind regards

    robert