So, how about this happens: I add a link to my reading queue. This _downloads the content_ but then saves it to cache. The page isn't rendered. It doesn't even open as a tab, but as some sort of reading queue, linked by context to where I opened it from, date, and other related metadata, plus more I can add (tags, etc.), later.
If I want it rendered in a clean "Instapaper" view, I get that too.
If it's ephemera, it clears automatically. If I want to have it stick around, that too.
When I actually _do_ load it up, it's reading locally from disk. This is pretty much how Readability itself works, in the app versions, and it's quick even on low-powered devices such as my rather old HTC Incredible Android phone (faster than most Web pages these days, and rather more compatible as I'm now multiple revs out of date).
As for SWF and Javascript: I tend to keep both disabled by default, and for most content, neither SWF nor Javascript are generally meaningful. There's the odd site which fails utterly to render without them (it's more than a tad bit ironic that Google's own blogging platform is one of the worse offenders), but that's pretty much the minority.
If I want it rendered in a clean "Instapaper" view, I get that too.
If it's ephemera, it clears automatically. If I want to have it stick around, that too.
When I actually _do_ load it up, it's reading locally from disk. This is pretty much how Readability itself works, in the app versions, and it's quick even on low-powered devices such as my rather old HTC Incredible Android phone (faster than most Web pages these days, and rather more compatible as I'm now multiple revs out of date).
As for SWF and Javascript: I tend to keep both disabled by default, and for most content, neither SWF nor Javascript are generally meaningful. There's the odd site which fails utterly to render without them (it's more than a tad bit ironic that Google's own blogging platform is one of the worse offenders), but that's pretty much the minority.