may be found in the podcast 
http://www.drunkandretired.com/2005/06/drunkandretired-podcast-episode-
09.html.

I am considering using rails (as opposed to asp.net) so am wondering what 
y'all think of what these guys say.

In a nutshell, they say that Rails starts to get less appropriate for apps 
with transactions that encompass entities other than just the database. If 
the server side objects also modify the data, and particularly of the 
modified objects then affect other objects, then it can become very non-
trivial to handle all of that in Rails.

Any feedback on this from experienced Rails folk would be most appreciated.

Cheers,
David Balick