I guess if you were doing something very weird, where Rails would really get in the way, it might make sense. And I've seen it end up being a piece of big apps, just not the main web interface.
I have found that I can write 10-20 lines of code and replace just about any plugin, and that makes the app far less complex, particularly when you think of how messy and undisciplined many rails plugins are.
I realized that rails offers the biggest benefit if your site uses TONS of forms. It's really not that big a deal to write a few forms by hand, and it makes using client side validation easier and cleaner.
I also love datamapper.
There just aren't that many moving parts, so there's very little that can go wrong, and there's no hidden magic, which is what has been making my life hell in the Rails 3 beta.
Also, Sinatra is fast. I just did a quick benchmark (ab -n 1000 -c 5 -k) on my laptop, and the scores were impressive. In the same rackup server, a bare Rack app did 4932 req/sec, Sinatra did 3169 req/sec, and the Rails 3 beta managed... 214 req/sec.
Here's the link for the lazy: http://monkrb.com/
I especially recommend it for when you want to hack up something small, useful and lightning quick. Rails is great, but sometimes it starts to feel like a very large hammer, when many web app ideas start out as small nails. Sinatra is a nailgun.