Padrino developer here. I also like monkrb but if you check out the Padrino guides (http://www.padrinorb.com/guides http://www.padrinorb.com/guides) you will se

Padrino developer here. I also like monkrb but if you check out the Padrino guides (http://www.padrinorb.com/guides http://www.padrinorb.com/guides) you will see that Padrino is quite a bit more full-featured but also modular. You can enable / disable various features of Padrino and even include certain pieces in existing Sinatra apps. Our team has used Rails and Sinatra both extensively for contract work and I would argue if you give Padrino + Sinatra a try that you will find it does not defeat the mentality of Sinatra. Instead Padrino simply complements the existing feature set with optional enhancements you might frequently need such as form helpers, tag helpers, localization, mailers and more. I agree that community support for Sinatra and Padrino are considerably lacking in comparison to Rails. I don't think this is something that cannot be fixed however. Sinatra has only recently hit 1.0 stable which means that the community has just begun to grow. I can say our team at least is committed to helping anyone with problems associated with Sinatra/Padrino. Feel free to post any issues here: http://github.com/padrino/padrino-framework/issues http://github.com/padrino/padrino-framework/issues if you find any specific problems. Thanks guys!