Only thing I'm keen for is the run_later fixes for using with passenger...
Since I only have one app that needs run_later in production and that is
only for updating something once a month. I simply spool up a thin instance
on another port and update. Shut it down after it is done and I'm on my way.

I've nearly finished a 2nd production merb app and everything is great :)

All the funky stuff coming in the router would be "nice to have" - it is not
like I need them or my app wont work...

Merb right now works really well and is very flexible. I say kudos to the
merb dev team and thanks for a solid framework that lets me get on with what
I want to do ;)

Nick

On Sun, Jun 28, 2009 at 1:51 PM, Ezra Zygmuntowicz <[email protected]>wrote:

>
>
> On Jun 27, 2009, at 8:34 PM, MyMerb wrote:
>
> >
> > Hi,
>
>
>
>        I'd like to chime in and say that I am still happily building apps
> with merb, http://engineyard.com/solo is built on merb. I don't find
> that there is anything I'm missing or that there are any features or
> major bugs stopping me from building apps with merb.
>
>        If merb works for you then use it, it is very stable and runs well
> in
> production. If you need the newest shiniest features all the time then
> rails is probably getting more love these days and may be a better
> option for you.
>
>        I'll let Yehuda and Matt chime in on the other questions
> specifically
> but I just wanted to say that merb is solid as is, it works and runs
> very well in production. I think merb is kind of feature complete and
> extensible enough that you can build whatever you want with it as a
> solid foundation.
>
> Cheers-
> Ezra (happy merb user)
>
>
>
>
> >
>

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