From: Robert Feldt <feldt@...>
Date: 2003-09-11T06:50:08+09:00
Subject: Re: webrick and ruby

Eric Hodel <drbrain@segment7.net> skrev den Wed, 10 Sep 2003 14:19:52 -0700:

> Well, once you add Borges, you'll not need amrita or fastcgi...
>
But then your code will not be separated from the skin/presentation, eh?
This seems to me to be one of the strengths of the amrita approach.
Not that I'm an expert in any of them (just checked them out) but from
a cursory look at borges the tight coupling between logic and presentation
stands out as annoying. Is this something that is being adressed or is
the tight coupling a "feature"?

More q's on borges:

Can it not be a performance issue that you regenerate the html
from scratch in each component? At least that was my impression
from the few borges examples? I guess you can avoid that by using
a different (template-based) renderer though. But this is probably
premature optimization on my part anyway... ;)

Do you have any larger examples showing the strength of the
borges approach? It is theoretically appealing and sort of
feels right but since its a different framework
than the predominant ones (sessions) I think you need to
really write it on our noses for us to get it :). Does
it give real advantages in real use? What are the downsides? Problematic
to disallow the back-button in situations where it shouldn't be allowed?

Why don't we take some more complex web app (phpbb2?) and rewrite
it in borges w. webrick? We can even "borrow" their themes and templates so its really "only" the code/php that we need to redo in
ruby.

Regards,

Robert