Comment Re:unless you need it wait... (Score 1) 149
There's a massive difference between knowing there are likely bugs in your software and believing that the day a fix or patch comes out it doesn't introduce new issues.
Microsoft, and pretty much every other software vendor I've ever seen have demonstrated time and time again that they're incapable of releasing updates without breaking something else.
So, we let the reckless and the silly be the beta testers, and wait until the dust settles. And, that's fine, because we can simply choose to wait to apply the fix for a while.
Microsoft wants to go to a "break first and fix it later" approach, and that's just asinine. Because it isn't their computers which will be broken in the meantime.
Sometimes you just have to ship the product.
Sure you do. But don't be surprised that your users refuse to be your beta testers and wait for more people to do that. Your QA is your problem, and I have no intention of making it mine.
The people who go "oh, boy, a brand new update" provide the valuable service to the rest of us of being test subjects. And they can live with the consequences.
The rest of us, well, after the first bunch of times we've learned our lesson.
So, be my guest. Run through the fresh steaming shit with reckless abandon. But I won't. Because I've seen Microsoft updates be broken upon release quite a few times, as I have from pretty much every other vendor.