11–20 of 159 posts
Microsoft has turned Windows Update into a cancer that is the single reason I am going to abandon their platform in future machine purchases. Can't believe I'm longing for the days of Vista (well post-SP1).
It's not clear from the article whether this was just an old long-standing bug that has now gotten attention, or if they really broke a basic piece of functionality that has been around since at least XP if not earlier. I'm not surprised either way, but unfortunately I'm leaning toward the latter. I don't think I'm the only one when I say I want Microsoft to quit messing around with Windows --- just fix the severe se…
It's not clear from the article whether this was just an old long-standing bug that has now gotten attention, or if they really broke a basic piece of functionality that has been around since at least XP if not earlier. I'm not surprised either way, but unfortunately I'm leaning toward the latter. I don't think I'm the only one when I say I want Microsoft to quit messing around with Windows --- just fix the severe se…
Earlier quoted context omitted.
I see what you’re saying, but Microsoft is forcing the industry on a treadmill to upgrade as quickly as possible as they aggressively break stuff on their quest the twiddle Windows twice a year. They need to embrace quality control. Handling zip files is a basic file system function in 2018. If they are fucking up basic operations like this, imagine how bad other parts of Windows are now.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
Yeah, sure. To hell with reliability, let's have features instead.
Reminds of chinese android forks.
Like, it’s understandable that supporting so many chipsets is hard but it really seems like they were doing a better job 10 years ago.
Yikes. This sounds, however, like a completely different bug, if it is only triggered by unzipping archives. I'm sure that the situation is more complicated than it looks - because it looks like there is just a shocking lack of QA testing being done, if basic edge cases like this are resulting in undefined behavior.
1. https://blog.ctm-it.com/it-support/blogs/matt-cannon/2013/49...
Earlier quoted context omitted.
I see what you’re saying, but Microsoft is forcing the industry on a treadmill to upgrade as quickly as possible as they aggressively break stuff on their quest the twiddle Windows twice a year. They need to embrace quality control. Handling zip files is a basic file system function in 2018. If they are fucking up basic operations like this, imagine how bad other parts of Windows are now.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
Earlier quoted context omitted.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
>the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Yeah, sure. To hell with reliability, let's have features instead. Reminds of chinese android forks.
Some are users like you who get emotionally upset about bugs.
Then I know others, like me, who simply acknowledge a coding error, or a future fix.
It makes dealing with QA difficult sometimes. What should be a scientific CS debugging meeting turns into an emotional tear-filled bug crying session.
Why get so upset? Seems "out of scope".
Earlier quoted context omitted.
I see what you’re saying, but Microsoft is forcing the industry on a treadmill to upgrade as quickly as possible as they aggressively break stuff on their quest the twiddle Windows twice a year. They need to embrace quality control. Handling zip files is a basic file system function in 2018. If they are fucking up basic operations like this, imagine how bad other parts of Windows are now.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
Earlier quoted context omitted.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
Somewhere at Microsoft some bean counters decided that formal QA was costing them too much and “agile” was a perfect excuse to scuttle QA (move fast and break things.) It’s bullshit that has been propagated throughout the software industry. “Well, Microsoft doesn’t do it this way anymore so...”. I work for an MS partner and this is exactly what’s happening in-house here. You’re just making your customers the beta tes…