I don't care if it is bad UX, I prefer it. I also turn off all the different types of preloading in Chrome, but that's another story.

The loading of a page hardly takes any time at all, and I generally have to reload the page when I finally get to older tabs anyways. And, this is silly, but it feels wasteful to have all tabs loaded all the time when I'm only using one or a few at any given moment.

Also I wouldn't mind if someone invented the "next great thing" to get us away from tabs. They are unwieldy, encourage tab-hoarding, and it is difficult to quickly locate a specific tab within a nontrivial number of open tabs. My overloaded tab bar causes more anguish than my email inbox.

We used to do this in Chrome in our pre-release days. It was annoying to use so we turned it off. The downside is that our session restore startup time could definitely be better for large numbers of tabs. We could do a better job of prioritizing loads. The right balance is doing the right thing for the user without exposing an implementation detail IMO.

Except for users that have dozens of tabs loaded because they're digital packrats, and don't care about most of them most of the time.

What about throttled loading ? processing wise, what is in the background will have 5% cpu allocated.

This seems like an issue only power users will have for the most part. Firefox even has an option to disable this for power users.

However, with that being said, I'm not a big fan. I think agumonkey's throttled loading is a nice idea though.

Off-topic: has anyone on HN spent time cataloguing either good UX choices or bad UX choices in today's web? I'm slowly beginning to take interest in user experience design (I'm a backend developer).

The author is confused.