This problem has been ongoing for decades in the computerized world.
When I worked for the Veterinary computer company, I used to dread the mornings after an update had been introduced.
I was in hardware support, which meant every piece of hardware plus OS that was attached.
So why would I dread the day after an update? Invariably we would get the calls about a peripheral not working anymore. "It worked yesterday but we applied the update and today it does not work." Software support kicked the complaint over to us as we were hardware support. We would talk to programming and they would say not us we did not touch that part of the code.
Needless to say somewhere down the line it would be found that a piece of code somehow inexplicitly changed how the program handled the peripheral.
Why do I bring this up. This was on a much smaller scale, and the program cost way more than MS ever thought of charging and it still happened. We had 6 programmers on staff. That is how small this operation was, and even they did not anticipate these problems.
Oh and this was before the Windows Craze and early on in the Mac craze. (My supervisor did not do windows he was a Mac person) I ended up being given a small job of working with those who wanted to use Windows 3.11 with their equipment. Otherwise we only supported, UNIX/XENIX, DOS (DRDOS), Lantastic and Novell.
Stewart At 01:08 PM 1/5/2009, you wrote:
I think it's easy to assume MS should have run a test for leap years, perhaps they only checked to see if dates functioned properly. My contention isn't that MS shouldn't have done more, but that most companies don't do more. David's example is evident that Apple doesn't check everything. Checking just the sheer number of security updates Apple applies to OS X over time it's clear they don't check everything, and it's my belief they can't. Or the product would never be released. The iphone 2.1 update was mainly pushed out as solely a bug fix for the problems in 2.0. What is the difference? Obviously Apple doesn't check it's OWN code even under Tom's standards.
Rev. Stewart A. Marshall mailto:[email protected] Prince of Peace www.princeofpeaceozark.org Ozark, AL SL 82 ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
