> Endless pagination should not break deep linking. I'm glad you mentioned this. I'd take badly implemented traditional pagination over badly implemented infinite scrolling any time. For the worst of both worlds, take a look at Microsoft Connect. It combines traditional pagination with the dynamic-loading approach normally found in infinite scrolling implementations. Content is broken up into pages, yet the back/forward/refresh buttons are non-functional (and don't even think about trying to open results pages in different tabs - all the links are JavaScript).

@Paulmorriss: > The trouble with high resolution PC displays is that Windows 7 and earlier doesn't scale up well. You can increase the font size, but that doesn't make everything scale up, so some things you need to click on are very small. Also, not everyone tests their applications with different font sizes, so you get strange effects with bigger fonts. Well-behaved Windows applications should scale up all user interface elements, and in general the OS itself has been pretty good at doing this since Windows Vista. Regrettably, making programs that look good at multiple DPIs is harder than it should be: try getting pixel-perfect bitmap images in a WPF application at multiple DPIs, for example. WinRT at least provides built-in support for multiple-DPI bitmap images, but until that framework is made to work on the desktop, it's useless for many classes of programs. As for being in a post-PC era, can we keep the high-resolution screens and leave the walled gardens?

From a privacy point of view, I rather like being able to keep accounts at different websites entirely separate. This kind of system might be acceptable provided that it remained entirely optional, which is impossible to guarantee.

Does the lack of VT-d support noticeably hurt the i7-2600K's virtualisation performance relative to that of the i7-2600, or are casual users (who happen to run VMs) unlikely to notice?