On Dec 12, 2005, at 1:54 PM, Ido M. Tamir wrote:
On Monday 12 December 2005 12:03, Erik Hatcher wrote:
On Dec 8, 2005, at 4:09 PM, Konstantin Ignatyev wrote:
Personally I see no reasons to worry about RoR yet.
No worries at all, you're right. I'm building the front-end of my
main project in RoR, and love it.
How is your back-end implemented?
Currently it is two Java-based web services. SOAP calls to Kowari
(an open-source RDF engine) and XML-RPC calls to a custom Lucene
search server.
Since the whole thread anyway goes off topic with regards to
tapestry, may I ask you some questions?
Sure thing.
RoR is here and now, and very effective at what it's designed for.
I'm using it, and very happy with it. Is it perfect? No. But it
lets me get the job done cleanly and mostly importantly, with
enjoyment.
a) What do you think about ActiveRecord vs Hibernate?
Never used Hibernate (I used Cayenne for a bit though). And I've not
done much with ActiveRecord yet. From what I've seen its an
acceptable solution, though perhaps not as "enterprisey" as the
heavier J2EE solutions like Hibernate.
b) When will RoR get nice reusable components like tapestry?
Does it need it? That's a question I ask myself. It would be nice,
but there are so many helpers and integration with AJAX and
JavaScript and a facility to do reusable templates via partials and
"components" (a reusable @Block basically) that something more
Tapestry-like hasn't really been a pressing need for me.
There are other templating options in Rails, with Amrita being one.
It is a very clean separation between HTML and logic, with templates
being super clean and pieces replaced by id's (sound familiar?). I
don't know whether Amrita does anything on request processing, or
only template rendering.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
