Linked by Thom Holwerda on Wed 29th Aug 2007 21:57 UTC, submitted by Kroc
Thread beginning with comment 266830
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
The Autopatcher folks getting a nice job or not is hardly the issue being discussed here. MS shutting down a useful community project that was helping allot of people, to witch they have no competing solution or valid replacement, is.
I'm sure people can come up with plenty of reasons for why they did it, and some of them might even sound justified. It still does nothing to ease the burden on system builders and support engineers though.
You can try to polish it, dress it up and cover it with perfume, but at the end of the day, a turd is still a turd.






Member since:
2007-02-22
It looks like Microsoft asked politely, and they took it down politely.
And who knows? The Autopatcher folks, now that they've shown they can work with the Windows systems on a deep level, just might find a nice employment contract hitting their desks soon. Especially with his closing line -- "the end of AutoPatcher as we know it." Not "the end of AutoPatcher."
See the example of Sysinternals for what I mean.