Latest Windows 10 Update Has Yet Another File-Managing Issue (gizmodo.com.au)
An anonymous reader quotes Gizmodo:
When it was discovered earlier this month that the 1809 build of Windows 10 was deleting user files just because, Microsoft halted the update until the problem was fixed. Shame, then, that another not-as-bad-but-still-bad file overwriting bug has now reared its head. in 1809, overwriting files by extracting from an archive using File Explorer doesn't result in an overwrite prompt dialogue and also doesn't replace any files at all; it just fails silently. There are also some reports that it did overwrite items, but did so silently without asking.
Ars Technica speculates that there's a larger program with Microsoft's testing process: [M]any of the preview builds had a bug wherein deleting a directory that was synced to OneDrive crashed the machine. Not only was this bug integrated into the Windows code, it was allowed to ship to end users. This tells us some fundamental things about how Windows is being developed. Either tests do not exist at all for this code (and I've been told that yes, it's permitted to integrate code without tests, though I would hope this isn't the norm), or test failures are being regarded as acceptable, non-blocking issues, and developers are being allowed to integrate code that they know doesn't work properly...
Microsoft's new development process has, proportionately, a greater amount of time spent writing new features, and a reduced amount of time stabilizing and fixing those features. That would be fine if the quality of the features were higher to start with, with the testing infrastructure to support it and higher standards before new code was integrated. But the experience with Windows 10 thus far is that Microsoft hasn't developed the processes and systems needed to sustain this new approach.
Ars Technica speculates that there's a larger program with Microsoft's testing process: [M]any of the preview builds had a bug wherein deleting a directory that was synced to OneDrive crashed the machine. Not only was this bug integrated into the Windows code, it was allowed to ship to end users. This tells us some fundamental things about how Windows is being developed. Either tests do not exist at all for this code (and I've been told that yes, it's permitted to integrate code without tests, though I would hope this isn't the norm), or test failures are being regarded as acceptable, non-blocking issues, and developers are being allowed to integrate code that they know doesn't work properly...
Microsoft's new development process has, proportionately, a greater amount of time spent writing new features, and a reduced amount of time stabilizing and fixing those features. That would be fine if the quality of the features were higher to start with, with the testing infrastructure to support it and higher standards before new code was integrated. But the experience with Windows 10 thus far is that Microsoft hasn't developed the processes and systems needed to sustain this new approach.
... computing. To turn PC's into locked down devices like phones. The masses are too stupid to understand what is happening and keep feeding all these companies money.
Wrong. The stupid masses now understand how stupid they really are, and buy tablets and smartphones instead of computers, which is why they're willing to now spend over $1000 on these "cheaper" devices. They already operate locked down devices, just like they drive locked down cars. Here's a little hint as to why; They don't want to maintain this shit, because they don't know how and don't want to learn. YOU pay good money to go visit a dentist at least once a year for the same damn reason; you don't have the expertise or the tools to maintain your teeth or do maintenance on them.
What you're quick to call the "stupid" masses ends up being the 90% of society who is NOT inclined to take up IT as a part-time hobby to maintain complex systems. The masses want shit that "just works" when they turn it on, even if that means they have less control and less functionality.
Watching PC software freedom and games being literally stolen and turned into "services" because the average person on our planet is fucking chimp level intelligence is pretty fucking disgusting.
And the reason software is turning into services is because it creates perpetual revenue streams. Greed N. Corruption is the CEO of US Capitalism, Inc. so don't be so stupidly surprised when greed is prioritized over cutting the customer a break.
But hey, if you really hate this shit, then go roll your own. There's always FOSS. Go for it instead of sitting on your ass bitching about it. You're asking the average idiot to buy a fully functional computer and learn to maintain it properly, so me asking you to go create your own OS is certainly fair.