On Apr 20, 2006, at 18:50, Giles B. wrote:
First of all, calm and peace!!!
There are a ton of Rails clones, basically at least one for every
language out there. I think Python has two or three.
A Rails clone is a lot of work, Django and Catalyst are the only
framewroks Rails-like to some extent (not clones). Which ton of
clones are you refering to?
Anyway – this idea here looks like a bit of a misconception:
Struts -> C layer
Hibernate -> M layer
JSP + Tiles -> V layer
These things really aren’t layers.
That was clearly a simplification, the introduction paragraph tried
to set the context of this simple table and the rest of the mail.
If you have three things on your
desktop, like, a file, an application which uses that file, and a
trashcan, those things aren’t distinct layers. That’s total Java
thinking, Rails doesn’t really have layers at that particular point in
I was using the word layer as in the MVC pattern, which is built-in
in Rails. I don’t understand what do you see strange there, it is
Anyway, sorry for the rant, but I do stand by it. On the whole
question of what the mailing and web services tools are in Rails,
there’s Active Mailer and Active Web Services.
The question was which mailer and web service solution would you put
on the Java side.
for corporate types. To put it simply, Rails will save you a ton of
time and a ton of money. The only real weakness I’m aware of for Rails
is that if you have a very large user base which needs very fast
performance, Java will be faster on the server side once you finally
get it up and running.
Sorry, I think you were reading a Rails versus Java question. The
original question was “how would you build something grosso modo
functionally similar with Java”, and I stressed it hadn’t to be
equivalent, because I know beforehand it can’t as of today.
That was an exercise in trying to see what aggregation of components
would a Java developer choose to get something similar at the
functional level, grosso modo. This is of course ill-defined, but it
is just an exercise. Obviously the Java aggregation is much more
heavy, much more verbose, lots of configuration files, lack of
integration, tag libraries are not comparable with helpers because
they are a PITA compared to helpers, etc. We already know that in
this list. But we are not comparing the solutions in that sense in