And obviously I meant a general-purpose Linux OS rather than Android or BoxeeBox since every Netflix subscriber who has wanted a Linux product has seen all the "it works on Android/BoxeeBox so it should work on Linux" posts around the net.

It works on Android/Boxee/Tivo/WDTV/other Linux-based hardware because of hardware-based DRM chips. This is why, for example, not all Android devices are supported by Netflix, or why the WDTV Live device was not supported but the WDTV Live Plus device was, or why Boxee supports Netflix on its physical hardware but did not do so in the now-dead software distribution.

Silverlight uses PlayReady DRM, which is what Netflix uses on devices without dedicated DRM hardware. PlayReady is designed to be cross-platform. The only thing stopping it from appearing on Linux is the cost of licensing PlayReady from Microsoft, building a Linux-compatible implementation (shouldn't be too difficult, as it already exists on OS X), and hooking it into Moonlight. But now Moonlight is dead, and nobody's going to pay for PlayReady licensing anyway, and even if they did it might still end up being incompatible with the GPL at some level needed to make it fully work.

I'm pretty sure that failure to properly signal turns and lane changes is actually illegal in more states than using a cell phone or texting while driving. So this must the be some newfangled we'll-fine-you-heavily-and-raise-your-insurance-rates kind of "nobody gives a shit".

Source?

In any case, the best possible world would be one where "most states are discouraging driving". Build liveable, walkable communities, with proper mixed-use development, green spaces, multi-use trails for pedestrians and bicycles, and good connections to public transit.

If the only way for a teen to buy groceries is by driving ten miles to a big-box Wal-Mart as the sole occupant of a seven-passenger SUV, then something is fundamentally broken.

This proxy claims TPB is down, however connecting directly to thepiratebay.se works perfectly (and has never been faster for me)

Your info is old. First, local sessions can and obviously do use graphic acceleration. Second, that functionality for remote sessions was added server-side in Win2k8 R2 and client-side in Win7sp1. But really, you've missed the point. Every local login session is effectively an RDP session, just running locally. That's a very simplified way of looking at it, but simplified is good when speaking at a high level.

*waves hand* These are not the movies you're looking for.

7. Windows Store
Humm.. No thanks?

See:

1. Interactive tiles
This might be useful once I get used to it.

Aside from the built-in apps, you will not get any other Live Tiles without going through the store.

5. Airplane mode
Ok.. Why not... I won't use it but a good idea..

and

14. Improved 3G support
Cool.

go together.

I was going to go through and point out everything wrong about all your other statements, but then I realized that you already summarized all of my feedback:

I am still an XP user atm...

Not a lot more to say about that. It's basically saying, "I'm still a Warty Warthog user atm ..." or, "I'm still a Debian Woody user atm ..." or for the Apple lovers, "I'm still a Jaguar user atm ..."

As far as Virtual Desktops go (Number 5), it is technically unfeasible, for reasons I don't quite remember. Something to do with the way Windows handles windows which has escaped me for the moment. Nevertheless, there are third party applications of varying quality that already implement this, to a varying degree.

Actually, virtual desktops should be trivial to do, and I'm surprised it hasn't been done yet. The key is Remote Desktop. Since XP/Server 2003, even your local console login session is essentially a remote desktop session, just optimized for being local. There's no reason why there couldn't be four or so local RDP sessions available to switch through on demand. It's effectively Fast User Switching, just without the actual user switching. It would even fit well with the RDP licensing for client OSes, where you can only have one login session active at a time (try it -- if you log in remotely, your local session locks). Processes in inactive sessions still run just fine, so the fact that your virtual desktops would technically be inactive RDP sessions would not affect running programs. Moving apps between desktops would be tricky or impossible, but on the other hand separation between desktop process spaces is potentially a good thing.

There are already hacks that allow multiple remote logins by the same user and multiple active logins, so in theory you could fake this yourself by connecting a couple of local-remote sessions and switching between them as needed.

Bring back visualbasic? (Number 6) No. Just no. That thing was a mess. Friends don't let friends script VB, drunk or otherwise.

Depending on the goal (the article was very vague, just asking for "a simple app development language"), this is either solved by Powershell (replaces batch script and vbscript) or by the new WinRT runtime with its Javascript interface and Expression Blend support for easily building GUIs. VB6 needs to stay dead, and IMHO VB.NET may as well follow it since there's really no benefit to using it over C#.

Whereas it's easy to find a previous revision now, particularly if you didn't save the specific version that you're looking for under a separate filename? Come now. Search for changes by date and time. Search for changes that add or remove specific phrases. Display overall document length as a function of time. Zoomable, scrollable display of changes over time, with annotated marks at each 'save' point.

The twentieth century called; they want their storage technology back. Hard drives don't have to spin anymore. Portable devices are all operating off batteries (or backed up by batteries) anyway, so power outages aren't the bogeyman they once were. Worst case scenario a memory cache is flushed to disk every five or ten minutes and we're no worse off than the current 'autosave'.

True, but not really a problem. Use the 'save' button to insert an annotation in the editing history instead of creating or fixing a file.