in response to http://madebymany.com/blog/replacing-rails-part-1-lets-go

I've been working on Rails for quite some time. It has also been a larger part of my life than I care to admit. I've been noticing the HN trend of wanting to replace Rails and feel people are starting to see the long-term writing on the wall.

1. Our apps are becoming more JS heavy and working with the asset pipeline is a pain

2. Despite Ruby being fun and flexible, it isn't fast. Not having a fast interpreter and having to support the C API hurts us. No plans to get rid of the GIL hurts us. Not having unity behind RubySpec hurt us. Not having concurrency primitives really really hurts us.

3. We aren't building new Ruby frameworks that are using great frameworks like Celluloid, which are also compatible with 'the Rails' (i.e ActiveRecord or ActionController) preventing easy migration and usage of great gems like devise. This is major.

So the reasons why we'd choose Rails are starting to slip but there are no better alternatives and that is mostly because of the very very rich gem ecosystem that handles so much for you.