Well, I was thinking the same way as Ahsan Ali, would we lose the
lightweight framework?? But it seems the main effort will be to make smthing
called "rails-core" , similar to merb-core....
Let's wait and c....

___________________________
Eng Khaled alHabache
http://www.khelll.com



On Wed, Dec 24, 2008 at 5:54 AM, Matthew Beale <[email protected]> wrote:

>
> Ok, so I'm facing this with a smile on my face.
>
> I didn't mind being pushed into merb at first.  The benefits once I
> worked around the smaller feature-set were significant enough, but we
> sunk a lot of time into making merb 0.9 dance (porting in house plugins,
> workling).  The merb 1.0 transition was terrible though, and we had to
> sink a whole bunch more time into not losing our upgrade path (you
> *need* to use a thread and worker for deployment? gems changing without
> new version numbers?).
>
> And now a THIRD transition to something new this spring.  I really hope
> this one is a damn bit smoother.  I guess it's the last though.
>
> That's my smoldering outburst.  Time to grin and bear and maybe remember
> your Joel Spolsky:
>
> http://www.joelonsoftware.com/articles/fog0000000069.html
>
> I'm very excited to see the great parts of Merb merged into the Rails
> codebase.  I expect great things from great people working together on
> great code!
>
> --
> Matthew Beale :: 607 227 0871
> Resume & Portfolio @ http://madhatted.com
>
> On Tue, 2008-12-23 at 23:38 +0300, Michael Klishin wrote:
> >
> > On 23.12.2008, at 23:25, Kyle Drake wrote:
> >
> > > What's the skinny guys? Is this an early April Fools joke, or the
> > > real deal?
> >
> >
> > Real deal.
> >
> > MK
> >
> >
> > >
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to