To view parent comment, click here.
To read all comments associated with this story, please click here.
True,
But when I called them to report the possible problem I had the following phone conversation (and I kid you not):
Gilboa: "Microsoft is auto-pushing their search engine..."
IT: "We know"
Gilboa: "It may slow people's computer down"
IT: "... Naah! It's integrated into the desktop... it doesn't slow the machine down"
Gilboa: "Argh. If people need it, they'll install it. People who don't need it will needlessly suffer!"
IT: "But we tested it!"
Gilboa: "On what machine? How loaded was the machine? For how long did you 'test' it?"
IT: "Err... I... we... tested it"
Gilboa: "Most people don't need it. It'll slow the machine down... Don't let MS auto-install it."
IT: "But we tested it..."
Gilboa: Click.
... Now this is what I call MSDN mentality...
- Gilboa
Edited 2007-10-30 10:26






Member since:
2005-07-06
It wasn't an accident... they were just testing how far they can go without being detected.
Think about it - in most cases, users will not detect this update when its being installed; when their machine starts slowing down (as mine did *) they'll either disable/remove it (if they know what they are doing), use it (if they need it - instead of Google search) or upgrade their machine ("because it's too slow") switching to Vista instead.
I may sound paranoid, but what exactly did Microsoft lose because of this mistake?
- Gilboa
* My workplace doesn't use auto-update; They push authorized updates down-stream only after they test them; however, being an incompetent bunch, they chose to authorize this update even after I, and others like me called to warn them about this update. Needless to say they are enjoying the joy of having the number of support calls quadruple.
Lucky for me I mostly use the Windows XP machine to read mail
Edited 2007-10-30 06:14