From a user standpoint, I can say that because having to navigate through a website to return to a previous location is slower than simply clicking the button assigned to my browser's "back" function. Regardless of what technological advances are made in the future, this will never change as long as dynamically scripted websites do not obey standard browser controls.

Actually, there's libraries like jQuery that lets browser history function as intended, but they're sometimes cumbersome to implement.

To be honest, browsers should adapt to AJAX rather than the other way around, IMO.

"Shaving a few milliseconds off page load times" is hardly the only reason why AJAX is a good idea; users who have disabled browser cache drive bandwidth costs up by constantly re-requesting images, to mention one thing.

Though I do agree that there should be a vote once there is a wide selection of good themes to determine the default one.

The problem with doing a vote is that the people with visual impairments will vote for the theme that suits them best, which is dandy in general except that visual impairments themes usually look like garbage to those without said impairments.

I for one would hate having a theme with giant fonts as the default for any site, even though I run 1920x1200.

Maybe compiling it into a CHM file will reduce its size? I have no knowledge on how this is done or if its searchability is sufficient for your (and your potential "client" base's) needs, but if it is, it could be worth looking into to avoid having to use a full webserver.

My eyes are sort of fubar'd too, my left eye sees close stuff fine but blurs stuff further away than 30cm, and my right eye is the other way around.
I don't know the fancy terms for those two things XD

Neither of these services will have any noticeable impact on performance, since Superfetch is explicitly designed to relinquish resources whenever a running application asks for them and Windows Search not only doesn't continuously index (unless you were smart enough to index some temp folder or something :p) but it also doesn't index when you're running resource heavy applications.

For what I just said to be correct, I'm assuming Vista (Superfetch) and/or Windows Search 4.0.

And I don't know of anyone reasonable who thinks that's an argument Blizz would lose.

That actually makes quite a bit of sense, but didn't I read somewhere in this thread that it's just guidelines and not an officially agreed upon ToS that you had to sign?
Maybe they will introduce this in the next patch, who knows.

Even so, would it still hold water in a court of law? I mean the ToS states you're not allowed to bot, but if you get caught you only get banned, not sued.