all I want is for merb 1.0.x to be refined and get the bugs out. I don't have much love for slices or any other form of plugin. I just want a simple, consistent, extremely well-tested API.
I cannot think of anything in merb 2.0 that I was holding my breath for. Jon On Dec 26, 6:21 am, "Matt Aimonetti" <[email protected]> wrote: > Samo: fair enough. However I strongly believe that in 6 to 9 months, you > will really want to migrate to Rails 3.0 to get all the stuff we promised > will be in Merb 2.0 > > One thing I believe most merbists will want is better perfs and better > slices. Even though I can't promise anything yet, but with the focus on > Rack, refactoring and the two teams working on modularity and performance, I > really expect Rails 3.0 to be super attractive to all the Merb developers :) > > - Matt > > On Thu, Dec 25, 2008 at 12:24 PM, Samo Korosec <[email protected]> wrote: > > > I know, I was just trying to explain the motivations behind some of > > the nervousness. > > > I'll just continue with merb for the next 6 months or so, and set > > aside some time for a possible migration later on and I don't expect > > it will be a big one. Worst case I stay with merb, which is fine > > enough for my needs as it is. :-P > > > On 25 Dez., 20:41, "Matt Aimonetti" <[email protected]> wrote: > > > I agree with Brian. > > > > Samo, you don't have to read the rails source code, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
