If your company wants to deploy VDI they'll figure out the connectivity requirements soon enough.

You're right, though - any kind of network or server outage has people twiddling their thumbs while you're still paying them. Not ideal.

The main complaints I see about VDI, aside from connectivity issues, is that it "isn't fast enough" to play video and games. Big deal. The majority of corporates are supposed to be working in Office-like apps typing documents, editing spreadsheets or pulling together slideshows - no video requirement there. Big bosses don't want you to access YouTube or whatever other time-wasting video sites you like to inhabit.

The minority of people actually needing physical desktops (for things such as network sniffers and maintenance) won't be on VDI.

In the original Tron, actors' faces were the only exposed part (the rest was "suit"), so they were actually the only realistic part inside the computer in the film. I don't think the makers of Tron: Legacy have an excuse for pulling another Polar Express.

I for one am yet to see any major improvements in speech recognition in the last ten years. It seems that it plateaued around 1995-2000 and hasn't had any decent improvements since.

Meanwhile, speech recognition has seen an increase in deployments in things such as:

• voice-driven menu systems... "I'm sorry, did you say 'put me through to an terminator'?", and
• speech-to-text voicemail... Telstra in Australia is a classic for this, with voicemail SMS's being nearly incomprehensible in conjunction with changing peoples' names such as "Royce" into something completely different such as "Melissa". wtf?

Speech recognition still has a long way to go me thinks.

Can I sell you a clue?

Please?

You only have to step very slightly outside of the core .NET namespaces (system.*) before .NET has problems being portable between Windows 7, Vista, and XP. Even System.Net.* behaves slightly differently on each of those platforms.

As already mentioned above, the multimeter in the picture is reading 2.164 megaohms which is quite a high resistance and would make no difference at all to the operation of the Kindle.

It seems that the blog owner has realised their mistake and replaced their blog entry with the content of another, but not before it made it's way into Google Cache

For those interesting in seeing the high-resolution "Oopsie" image, it is here.

Hear! Hear! This from TFA:

Um, excuse me? What business is it of yours? They've already told you what types of data have been sniffed. Why do you need to see it?

Which, I might point out, didn't stop them from silently installing the "Microsoft .NET Framework Assistant" add-on in the Firefox browser so Firefox users would be vulnerable to attack ^h^h^h...^h^h^h able to install ClickOnce applications hosted on the web.

Yes, that is supposed to be one of the selling points (in relation to Many Eyes), however, lest we forget... http://cyberinsecure.com/adware-back-door-in-firefox-language-pack/

This particular issue wasn't in the core app, though, it found it's way in via a language pack. It just demonstrates that FOSS isn't immune.

Also from that link...

Oh, my sides! I guess that was an epic FAIL for the NSA then? (Either that, or Windows might actually have been more vulnerable to attack without their help.)

Thank you!

Somebody probably got confused because TFA is titled, "Wik-Bee Leaks: EPA Document Shows It Knowingly Allowed Pesticide That Kills Honey Bees"

Your example doesn't quite fit the definition. Whilst that was excellent thinking for the Apollo 13 mission it was essentially making a scrubber out of... a scrubber. The stupidity that led to the problem in the first place was that instead of using one type of scrubber throughout, the CM scrubbers were square and the LEM scrubbers were round - truly a square-peg-in-a-round-hole problem.