I find that stitching my own framework from quality open source components gives me a bit more flexibility than Rails (rails user since version 0.7) and lets me get closer to the metal when I need it. Your mileage may vary :)
And no, you're definitely not retarded.
I was thinking of something where you essentially write the whole app in ruby, and then it generates DataMapper models for your objects, sinatra routes to access the data, and js code to actually access the server and hook it up with your ui. Something more along those lines.
I first touched rails at 2.something, a bit before 3.0, but it was my first experience with MVC (that is, a single framework that handles all of your MVC) and I had a lot of mixed feelings about it. I still bounce around a lot but right now I'm leaning more towards "MVC is good".
https://github.com/danski/spah
What @angryamoeba (danski on github) is trying to do, in so far as i have understood it is to address the problem that say twitter has in that it loads up a dumb empty template, and then you have to wait for the JS app to boot up and populate your page.
Instead what he's tried to do is specify a consistent way to specify data in HTML documents (via data attributes), and a framework for syncing modifications to data between the client and server (and this is bi-directional).
That way, if you're doing a cold boot, data is specified in page, and if the client has already loaded an object, full pages/data don't have to be pulled down to the client when things change, and likewise full page state doesn't have to be shoved up to the server when the client changes something.