> You do know that Merb and Rails are merging, right? It might be easier > to update your app from Rails to Rails 3 (merb + rails) when it's > released.
I'm not sure that's a good reason to delay projects you were planning to use merb with, or stop developing with merb, or even stop contributing to merb itself. The reasons that attracted all of us to merb are still valid today, and will continue to be valid until Rails 3 is released *and* has proven itself to the community. Just because something new is coming doesn't mean you should delay working on something you'll enjoy. There will always be something new around the corner. When that new thing arrives if you decide to migrate to it, there will still be pain. You can't avoid that. But if you write nice clean code, with good specs, and test the behavior like a black box (just like Yehuda has been advocating) that pain should be minimized. Dan (dkubb) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
