There is of course also Groovy to look at. I've used Ruby and Groovy and Groovy seems to be a bit better (well, at least in terms of what libraries are available, you can use the standard Java API for example and as a result any other Java library)
Groovy looks cool because it has closures, something I constantly miss in java. Another thing to add to my list..
Edward, regarding Ruby on Rails it's not a direct comparison to tapestry as tapestry is a templating engine whereas RoR is a collection of tools useful for creating web applications. I haven't used RoR but follow news and comment on web app architectures closely. It gets an absolute panning in a recent article here: http://discuss.joelonsoftware.com/default.asp?joel.3.309321.8 One thing that I read again and again is that the bundled database backend is not strong.
If you're interested in the idea of Ruby on Rails, you might find turbogears interesting (turbogears.org). It was developed with a similar motivation as RoR - throw a bundle of existing tools together to create a convenient package. The SQL backend appears to be more powerful. Turbogears is written on top of python. I've only done a bit with it and don't yet have a good feel how it stacks up against tapestry, but all the things I want addressed in tapestry 3 (which I use) appear to have been improved in tapestry 4, so I'm not sure how it could turn out to be an improvement :) Tapestry's html/page/java separation has made it particularly effective for developing large complicated web systems. I suspect less structured systems will decay once a page in a web application gets to a moderate level of complexity. This sort of thing happens quickly if you're trying to keep the number of page clicks a user does down. But I'm still playing with the templating system in tg and might find a way to eat those words.
- C --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
