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]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
