Re: Ruby on Rails vs. WebObjects

We use Ruby, but we use no Rails.

We will continue using Ruby, but we will not start using Rails (after  
evaluating it). Rails has nothing comparable to EOF, and as it is  
currently being designed, it will not evolve into this direction. So  
this is no go for us.

So, what we do with AJAX. First we pray Apple fixes the WO design  
making it more XML and JS friendly. Second, we add our own WO/AJAX  
support when we need. I would love to donate our additions (some of  
them are really cool), but working on the largest dutch banking  
project in a decade or so is not exactly open-source promoting. But  
when phase 1 is in production, I would be glad to share our experience.

And before you start asking, yes, WO is well, and in a good shape,  
and banks here do not care if the system that is expected to handle  
€5x10^9 worth of transactions during the first year it is done in WO  
or any other technology as far as it works...

gt

P.S. What is exactly AJAX? Bunch of old technologies wrapped in fancy  
acronym and a lot of hype. It is fine to use AJAX-like techniques  
together with WO, but most of the existing AJAX frameworks are not  
applicable for us neither as source code, nor as design... So my  
first advise here - do not mix oranges and bananas! Learnt about AJAX  
from a book like the Pragmatic AJAX, but do your stuff enhancing WO  
and not bending it...

On Feb 28, 2006, at 6:16 PM, David LeBer wrote:

> My take after hearing his comparison is that if you really need  
> AJAX and don't want to try implementing that support in WO then you  
> might want to look at R on R. Other than that, I couldn't see any  
> compelling reason to switch. Other than it being open-source and  
> having the hype that is - not that those may not be compelling  
> reasons for some :-)

Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196