So that's the big question Jenny. Unfortunately since we don't have a good idea of what Rails3 is going to look like at this point... the advice has mainly been, continue as if you had no idea what Rails3/Merb2 was going to look like (i.e. hold off on conversion either way)
For myself, all my personal projects are going to continue being Merb/DM projects (particularly since i've really been enjoying using DM). The things i don't like about Rails are still in Rails, and will continue there until we start seeing Rails3 alphas and the like shaping up (which you can keep track of in wycats's branch of rails http://github.com/wycats/rails/tree/master , incidentally). Likewise all my Rails apps are going to hold off on the migration to Merb, now that Merb2 is going to be Rails3. -Ted On Tue, Jan 6, 2009 at 2:35 PM, Jenny <[email protected]> wrote: > > I'm wondering: I've a project that I've started in Merb. I want to > keep up-to-date, so I want it to upgrade along with merb. But now that > Merb is merging, which would be easier/better to go from merb to Rails > 3.0, or from Rails 2.0 to Rails 3.0? If any of you know, or could > conjecture, it would be appreciated. It seems like I've hit several > snags converting my merb app to Rails 2.0, and I'm wondering if it's > worth it? > > -Jenny > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
