Re:Proper prior planning prevents poor performance (Score 1)

My guess is that the issues are more about the software requiring bug-specific behaviors. I had an opportunity to speak with one of the OS people a long time ago, they said that "Long Ago" Lotus 1-2-3 had a nasty habit of writing to files after Lotus told the OS to close the file handle. In the older versions of the OS, the OS didn't check to see if you were writing to a closed file handle, and wrote to the closed file. Then you update to the latest version of DOS, and all the sudden it breaks Lotus because now the OS cleans up after itself and correctly returns an error when you try writing to the closed file handle (which is probably ignored by Lotus, causing the save file to be corrupted somehow). Now who do you blame? MS for not getting the API right in the first place, or Lotus 1-2-3 for writing to the closed file handle, or MS fixing a bug? From what I remember, MS ended up adding code to detect that the application was Lotus and switching into a quirks kind of mode. Having to write fixes for all these crappy applications is why Windows is a POS. More towards the issues with drivers. A friend of mine's printer driver broke with XP SP2. We found out that how the printer driver worked was it has a service that hosted an application that spoke to the printer, and the driver spoke to the local application via TCP. MS firewall blocked it (cause open ports can expose vulnerabilities). I blame the printer company for writing a crappy 50meg printer driver that requires a network connection to print locally, not MS.