I have recently shifted my nascent project to Merb 1.1.0-pre (for Ruby 1.9.1 compatibility) and I'm very happy with it. Of course, I expect to eventually port to Rails 3, but by keeping all my hand-written code well organised and modular I hope to be able to regenerate the site using the new framework and fairly quickly incorporate my code into the new structures.
Mark From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Pollard Sent: 31 December 2009 21:23 To: [email protected] Subject: Re: [merb] Re: Framework choice for a new app We just started a new project at work with Merb and have been very happy. It's not as well documented as Rails, and while that does present some initial challenges onboarding new people, keeping the more junior people self-sufficient and understanding how certain features work, the benefits for us of Merb far outweigh the initial headaches. That said, I wouldn't be surprised if once Rails3 comes out and does everything it's promised to, we won't start working with it. Merb 1.x and Rails 2.x are your two main competing Ruby web stacks at the moment - and we like Merb. Rails3 will be a completely separate animal that will borrow ideas and design patterns from both projects, and looks very promising, However, I don't foresee updating your Merb 1.x or Rails 2.x app to Rails3 to be super-easy from either Merb or Rails. This is just my observations and opinion, and Yehuda will certainly have better insight in to this than I do. -J On Wed, Dec 30, 2009 at 9:50 AM, Jon Hancock <[email protected]> wrote: Martin, Which will be easier to port to Rails3? If you want ActiveRecord, I guess rails would be more straightforward port. Without ActiveRecord, I don't think it matters. If you want very simple, sinatra is nice. I stuck with merb for my new app simply because despite sinatra's simplicity, I had many techniques worked out with merb from a prior project. Rails 3 is a new thing. Moving to it when its stable enough is going to require a port without regard to which other ruby framework you have used. Clean code is your safest porting tool. Jon On Dec 30, 12:41 pm, MarkMT <[email protected]> wrote: > This would be a great opportunity for Yehuda to jump in and give an > update on where things are up to on Rails 3, with some > characterization of how Rails 3 and Merb 1.1 will be related in terms > of architecture, api and performance and some assessment of when it > will make sense for merb apps to be migrated to the new platform. At > the moment, in the absence of information, I haven't found a reason to > leave merb. > > > > Martin Mazur wrote: > > Hello, > > > I'm going to start development of a new app and I'm wondering which > > way to go on the framework choice. > > > I was leaning towards merb but since merb and rails are merging I'm > > unsure. > > > What I'm mostly interested in is which of the frameworks is more > > future "safe", which will be easier to port/upgrade to rails3? > > > And which will be supported by the community in the future? > > > Best Regards > > > -- > > phone: +46 (0)709 78 40 03 | e-mail: [email protected] | blog:http://blog.upplopp.se -- 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] <mailto:merb%[email protected]> . For more options, visit this group at http://groups.google.com/group/merb?hl=en. -- 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. -- 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.
