The one thing that has always put me off of Ruby on Rails is the upgrade story. It looks like a massive pain to keep updated, and an even bigger pain to bring up to date if you don't stay on the update treadmill.
I initially built my saas product in Rails. It was great, for a while.
Updating was a source of anxiety that led to rewriting the service in another language. It was a real pain... gem X would depend on Y. Y would need version Z of Ruby and Rails version W. You try to update X by updating Y and everything breaks apart. Same story for 15 other gems you depend on. You end up in a web of crazy dependencies. This is even worse if you use a heavy Rails engine (like rails admin, etc).
You eventually get backed into a corner and you "live with it" like the author of the post described, until you rewrite it.
The one thing that has always put me off of Ruby on Rails is the upgrade story. It looks like a massive pain to keep updated, and an even bigger pain to bring up to date if you don't stay on the update treadmill.
I initially built my saas product in Rails. It was great, for a while.
Updating was a source of anxiety that led to rewriting the service in another language. It was a real pain... gem X would depend on Y. Y would need version Z of Ruby and Rails version W. You try to update X by updating Y and everything breaks apart. Same story for 15 other gems you depend on. You end up in a web of crazy dependencies. This is even worse if you use a heavy Rails engine (like rails admin, etc).
You eventually get backed into a corner and you "live with it" like the author of the post described, until you rewrite it.