[officemonkey]

I just booted up Safari (for the first time since I installed Lion) and tried out the "Reading List".

The main reason I don't like it is that the reading list doesn't load the page until you click on it. When I create a tab, it loads and opens the page and it's ready when I navigate to it. I navigate to a reading list page and I have to wait a non-trivial amount of time for the page to load.

I understand why you would do this for a mobile browser (to reduce data charges for pages that might never be opened), but that doesn't matter to my desktop machine.

Safari could mostly fix this by preemptively loading the neighboring pages in your reading list. Until then, I'll stay with my tabs in Chrome, thanks.

[derefr]

> The main reason I don't like it is that the reading list doesn't load the page until you click on it. When I create a tab, it loads and opens the page and it's ready when I navigate to it.

If you've ever gone on a Wikipedia/TVTropes/Everything2/other-heavily-intralinked-website-here binge, you'd be thankful for the fact that the reading list doesn't load the pages you hand it until you're actually reading them. 3000 open tabs will kill any web browser I'm aware of; 3000 reading list entries is just 3000 items in a list.

[CognitiveLens]

I'm not sure I understand your reply. I think that officemonkey meant that in a serial list of "things to read", Reading List could cache the preceding and succeeding pages relative to the particular item you're on so that as you complete one page you can immediately jump to the next/previous page.

I agree, however, that Reading List does not address the "random access" approach to research, which is more along the lines of using tabs simultaneously, as intended.