Question

I moved my application off of Rails early in 2009 because I didn't need or want all of the features in that framework (ORM, MVC etc) and didn't like the large footprint we were generating (200Mb). Merb-core has been a great home for our application but I'm now wondering if we should move elsewhere now that Merb & Rails have merged.

Does anyone have advice on the following questions?

  • Should we stay on Merb?

  • Given the desire for a minimal footprint, is there any point trying to reimplement the app on Rails 3.x?

  • I have some experience with thin and Rack but use enough Merb features that the port wouldn't be painless - is it worth going 'down' to bare Rack?

Thanks, I appreciate that some of these are subjective but I hope that there are enough people who have used Merb and who have faced the same questions.

Just as an aside, the last question here about Merb was almost four months ago.

Was it helpful?

Solution

I have a couple of production apps running with Sinatra. It's light-weight and generally a pleasure to work with.

OTHER TIPS

Since Rails 3.x is more modular than before, you might want to have a look at it too. You can slim it down quite far. If you're going for a really minimal footprint, Sinatra is an excellent choice.

Does Merb not meet your needs anymore? I'm still using it. I've tried Rails 3 and it doesn't feel at all like the "Merb 2" I was promised; kind of just feels like Rails. As such I continue to use Merb for new projects. I have one I deployed this past summer and a larger project for an existing website that I am currently developing. Perhaps it's not a very popular framework, but it meets most of my goals and so far I've seen no reason to leave it behind.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top