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: 1. Make Rails 3 more appealing for merb developers. I see no path for this. 2. Get merb back up and running. I don't see enough community support for this, since the rug was pulled out from under it. People incorrectly see Rails 3 as having "solved" the problems merb originally solved. 3. Take advantage of Sinatra's momentum. Put our energy into a lightweight framework on top of it. Padrino <http://www.padrinorb.com/> comes to mind. ..tony.. On Fri, Jun 3, 2011 at 1:51 AM, pedro mg <[email protected]> wrote: > Hi, > > On Thu, Jun 2, 2011 at 10:27 PM, Tony Mann <[email protected]> wrote: > > We are going to stick with DM, at least for now. So the models can stay > > as-is. > > We just need to port the rest of the stack; ie. controllers, views, and > > helpers. And some of the merb-specific /lib code. > > If you need more info, let me know. > > If this is starting to bore the list, you can email me directly :-) > > let it flow, this is a good topic and this list needs this kind of activity > ;-) > > pedro > > -- > 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.
