[rubynerd]

I don't know about you, but every time I've attempted to use Sinatra for a project, it's either been for something that wouldn't ever see the light of production, or I've just ended up with franken-rails.

We had this problem at work: a Sinatra app that had pieces and pieces of ActiveSupport bolted on, and it got to the stage where we needed a beefier database than Redis before the CTO eventually generated a new rails app and transplanted the Sinatra app on top of it.

It's all well and good saying "use Sinatra", but when you get to the stage where you're adding ActiveRecord because it's the most mature ORM out there, it's usually late enough in the game that you're actually writing a poor excuse for a Rails application.

[Argorak]

I hear that sentiment a lot (I blogged about it here: [1]). Basically, "every time I use Sinatra, I ended up with franken-rails" means that Sinatra was either picked for the wrong reasons or misused. If you want to build something large based on Sinatra, for the love of $deity, please use organization systems people have built for you, be it Padrino, some Sinatra stack or something else. It doesn't mean that Sinatra is bad, but its often misunderstood.

[1]: http://www.asquera.de/opensource/2012/10/22/the-rails-monoth...