Helping early-stage companies turn great ideas into even greater products Rapid scale-up and dependable delivery with unsurprassed passion and experience Swift and predictable results combined with quality and cost performance
banner

Merb vs. RoR – which one to choose?

Bookmark and Share

The question seems to be rhetorical for those who are well familiar with Ruby frameworks. When asked the question, they would answer – hey, RoR rules the world, there’s no doubt in that! Still, on of our current projects at Cogniance was initially based on Merb, and we had to seriously think if it is worth while porting it to RoR. We’ve decided that the port is justified, after all.

And here are some of our key reasons for this decision:

1. Merb future is undefined due to forthcoming migration with Rails. Despite Merb’s author assurances, amount of work and buzz emerged around Merb have slightly decreased since the merge announcement.
2. Merb has a couple of  issues with bundler, mostly confirmed long time ago yet not fixed till now, here’s prooflink. This makes deployment a real hell. Also, Merb’s took Thor is also able to behave unpredictably.
3. Merb community is much smaller that Rails’ one. This means smaller knowledge base, less bugs fixed, less blog posts and questions asked and answered. Unfortunately, situation isn’t going to be better in a future.
4. Rails world have many times more ready, tested and working solutions comparing to Merb world. Compare number of different plug-ins for Rails and Merb, and you’ll get the picture.

Written by: Cogniance Ruby team

This entry was posted on Thursday, October 1st, 2009 at 12:11 pm and is filed under Web 2.0 technologies.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.

2 Responses to “Merb vs. RoR – which one to choose?”

Leave a Reply