As a correlary to this question... I'm learning Rails and Ruby from an experienced J2EE developer's perspective - which of these frameworks works well (in your experience) to managing legacy (i.e. pre-existing) databases and interacting with ESB?
On Sun, Aug 31, 2008 at 1:21 PM, Andreas Kirn <[EMAIL PROTECTED]> wrote: > > Rails is great for building a simple "dynamic" website or a quick > proof-of-concept app, but let's face it, it's too slow and rigid for > large web applications. At least in my experience. > > What I'm looking for is a lighter, more flexible framework that will let > me code in Ruby and use DataMapper without forcing me to conform to too > many silly conventions. So far, I've played with Merb > (http://merbivore.com/) and Ramaze (http://ramaze.net/). Pretty soon I > found myself favoring one over the other, but I'm curious as to the > experiences other developers might have had with these frameworks. Are > they stable and scalable enough to be ready for prime time? What about > ease of use, extensibility, helpers, community, etc? > > And, while we're at it, what about Camping > (http://code.whytheluckystiff.net/camping/), Nitro > (http://www.nitroproject.org/), Wuby (http://wuby.org/), Halcyon > (http://halcyon.rubyforge.org/), or Vintage > (http://vintage.devjavu.com/)? Have you used any of these frameworks? > Do you think any of them has the potential to become the framework of > choice for the more advanced developer? > > Btw, what happened to Sinatra? > > Andreas > > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
