The blog does not say what the contributor says it does. The closest it comes is noting that the links from the negative reviews never counted in the first place because the sites hosting the reviews used the "rel=nofollow" attribute on the links. What it does say is that they have altered the algorithm to punish bad businesses more effectively in response to the NYT article that suggested that being bad could be good for business.

Move along, nothing to see here!

Design your application to modularize the OS-dependent code away from the OS-independent code. When it comes time to port (if it ever happens) you should only have to worry about the OS-dependent stuff with minimal modification to the core of the application.

TCP/IP is routable, period. The "non-routable" blocks are simply IP addresses that can't be used across the Internet but will still work fine in an internal network. HP's users might need to talk to each other, but there's no reason for me to able to ping all of them from home.

This is obviously coming along with the increased focus on removing distractions from driving (cell phones, texting, DVDs, etc). The problem is that flying a plane has almost nothing in common with driving a car, beyond some rudimentary instrumentation similarities and the overall goal of getting from point A to point B. The skies are not crowded like a freeway--a pilot doesn't have to worry about the plane next to him cutting him off on the way to LAX, because there is no plane next to him--flight paths are planned well in advance. The pilot only has to worry about situations that can't be handled by auto pilot, like mechanical failure or turbulence.

So, in other words, the FAA is saying, "We want you to give your full attention to flying, but you can't do anything to keep yourself awake." I don't care how much sleep you get, a 17+ hour trans-Atlantic flight with nothing to do but check your instrumentation is going to bore you to sleep. In trying to improve flight safety, this is going to have the opposite effect.

Reading comprehension: I'm not advocating Virtual XP. I'm suggesting running MS-DOS 6.22 as the guest OS--that is, applying the same methodology as Windows 7's "Virtual XP" mode to use a "Virtual DOS" mode rather than emulating it (poorly) in the kernel via NTVDM.

Certainly the best way to eliminate this threat is to do away with the NTVDM altogether and use virtualization, similar to how Windows 7 Pro has "XP Mode." Microsoft should create a virtual HD (*.vhd) file with MS-DOS 6.22 installed on it and then offer it as a free download. Users could either use Virtual PC or the virtualization solution of their choice (VirtualBox, VMWare, etc).

DOSBox is also a decent solution, although it is geared more towards DOS games than to completely and accurately emulating MS-DOS.