There are times (testing frameworks) when it is undesirable to see the startup/teardown "chatter" of the Sinatra server.

For instance:

== Sinatra (v1.4.7) has taken the stage on 9101 for development with backup from Thin
Maximum connections set to 1024
Listening on 0.0.0.0:9101, CTRL+C to stop

and

== Sinatra has ended his set (crowd applauds)

The latter comes from quit! method.

Request a :quiet option to suppress these extraneous messages.

Motivation: See the ugliness of the solution for this problem: http://stackoverflow.com/questions/16183177/thread-safe-capturing-the-output-of-stdout