Anil Punjabi's Blog

When should you not use Ruby on Rails for a startup?

Let me start with the bad rap you might have heard about RoR first. 

Rails makes development go faster because you have to write less code to achieve the same functionality. This require a deeper understanding of how Rails does what it does. This might be a challenge for some developers that are proficient if either the back-end or the front-end, but not both.

Also, Rails is slow if you don’t tune it right. 

Some people complain that the Rails syntax is complicated. Yes it appeared to be a bit wonky in the first couple of months to me as well. 

After that digestion period though, development will fly. The flexibility and structure that Rails offers you will make adding new features a lot easier. 

This flexibility is often a desired capability for startups as they often need to tune their offering based on customer feedback. 

If you are building a startup where you can get by with using regular CMS systems (like Wordpress) or standard eCommerce platforms then you don’t need to worry about Rails.

If you are developing a platform from the ground up give Rails a chance.

More answers on Quora

When should you not use Ruby on Rails for a startup?