Sinatra pretty much serves my needs. I use DM with it. I've dabbled in Padrino a bit.
However, one's app *can* outgrow Sinatra, I've found. On Fri, Jun 24, 2011 at 2:17 PM, Tony Mann <[email protected]> wrote: > What makes you want to redirect efforts in developing Merb to Padrino >> ? The community ? For now, I'll stick to Merb. > > > I was just pondering whether we could leverage Sinatra's momentum. I > imagine that Padrino needs help, and Sinatra provides a great foundation. > Maybe we could take our learnings from Merb and use them to make something > like Padrino be a pack leader, as a genuine alternative to Rails. > > ..tony.. > > On Tue, Jun 21, 2011 at 12:55 PM, pedro mg <[email protected]> wrote: > >> Hi, >> >> On Fri, Jun 3, 2011 at 6:17 PM, Roy Wright <[email protected]> wrote: >> > Personally I've switched to Ramaze for an easy to understand, light >> weight >> > framework. I much prefer having to specify what I want versus discover >> the >> > magic recipes necessary to disable what I don't want. >> > >> > On Jun 3, 2011, at 11:48 AM, Tony Mann wrote: >> > >> > A thought, based on the "we gave up on our Rails 3 port" postings: >> > >> > Rails3 derived some benefits from having merb team work with them, but >> > ultimately Rails 3 does not appeal to merb developers. >> > >> > So to me, the integration of merb into Rails 3 was ultimately failure, >> since >> > the developer community was not well-served by it. This gives us three >> > choices: >> > >> > Make Rails 3 more appealing for merb developers. I see no path for this. >> > Get merb back up and running. I don't see enough community support for >> this, >> >> I'd love to see numbers on merb apps in production. Merb was growing >> steadily until the core developers had that "call for action" to work >> on a messed Rails. That was a breaking point in Merb timeline and >> teared its community apart. I still find Merb a smart project and >> pretty interesting framework. Because of its value we can't say "its >> dead". It isn't. Nicos is working on it, digging its source and >> working on interesting future solutions. >> >> It would be interesting to have a Merb::Conf (conference) to revamp >> its image as a working and smart ruby framework. >> >> > since the rug was pulled out from under it. People incorrectly see Rails >> 3 >> > as having "solved" the problems merb originally solved. >> > Take advantage of Sinatra's momentum. Put our energy into a lightweight >> > framework on top of it. Padrino comes to mind. >> >> Sinatra is interesting for its pure simplicity. I'm using it as a >> read-only "model" (API) for a Merb app. >> >> What makes you want to redirect efforts in developing Merb to Padrino >> ? The community ? For now, I'll stick to Merb. >> >> I will try to contact Ezra and Wycats and other commiters like SnuSnu >> to ask them how they see Merb right now, and how they see Merb related >> to other Ruby frameworks technically. >> >> best regards, >> @pedro_mg >> >> -- >> You received this message because you are subscribed to the Google Groups >> "merb" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/merb?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "merb" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > -- Chris Scott Transistor Software <http://www.transistorsoft.com> -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
