Earlier quoted context omitted.
Yes, Sinatra is a Ruby web framework. Sinatra is more of a "micro-framework" and puts you closer to the http method. Basically, the api mimics http more closely, you literally use get, put, post, and delete methods to define your routes and actions. In Sinatra, you define your routes in the same place where you program your Resource's functionality, so less mapping is required. In Rails, you have a separate controlle…
Also, if you want rapid prototyping, you should look into a document store such as Mongo. Not having to write migrations (as you would with ActiveRecord + Mysql) is huge. Also, your models can be more flexible. You can add keys to your document as needed. With Mysql, you need to have a migration to add the column.
Of course it depends on the problem, but working with hashes and arrays is simpler than the relational model, no?
I do concede the vast swaths of docs for AR, however AR is pretty complicated and issues arise that aren't well documented.