From: Don Dwoske <ddwoske@...>
Date: 2004-01-27T23:04:56+09:00
Subject: Re: choosing ruby?


I would recommend Ruby wherever appropriate, but in this case, I agree 
with Robert.  His list of reasons was sound, I won't repeat them.

The only thing I would disagree with in his recommendation, is that you 
*should* use an app framework - but not a fancy one.  Struts is too 
bloated for small apps and too big a learning curve.  But having 
something to easily do validation and unmarshalling of request 
parameters is useful.

I'd use maverick with throwaway controllers and velocity instead of 
struts and jsp.

http://mav.sourceforge.net

-don



> Considering all this I'd recommend to go for plain Java.  Reasons:
> 
>  - you're quite proficient in Java
> 
>  - the JSP / Servlet framework is there and not really
>    difficult to understand (IMHO) if you know web app
>    basics (HTTP, HTML, control flow etc.)  In your case
>    that seems sufficient, no need for some fancy web
>    app framework (don't use Struts)
> 
>  - not mixing languages means saving yourself a lot of effort and
>    a huge source of bugs
> 
>  - you might not even be allowed to use Ruby
>    (because of interpreter compilation)
> 
> Next would be Ruby since it is IMHO more easily learned than Perl and
> there are webrick, eruby and others.
> 
> I would not consider Perl since you don't benefit in this situation:
> Learning Ruby is easier and you don't need the additional speed that Perl
> exposes over Ruby for some applications.
> 
> Kind regards
> 
>     robert
>