One user's stupidity becomes Internet bait for something that's saved so, so much time.
I remember playing the backup & restore game when rebuilding my PC, which I just happened to do last night as I received a new SSD. I didn't have to worry about documents and thanks to a separate volume, redownloading my Steam library, either. That was a massive time save. And it didn't have to be OneDrive, it could have been any cloud sync service -- but OneDrive works just fine.
The user just fucked up and had a conniption fit on Tiktok.
OneDrive doesn't always work fine, though. I avoid it like the plague because a OneDrive screwup caused me loss of valuable data.
Was it user error? Maybe, maybe not, but that's irrelevant. If it's so easy to make an unrecoverable and catastrophic mistake, it's a tool that's too dangerous to use on the daily.
All I know is that a bunch of files reverted to very old versions and I found no way to recover from that. It was pure loss. How did it happen? I have no idea. But how doesn't matter at all to me. What matters to me is that OneDrive proved itself untrustworthy.
> If it's so easy to make an unrecoverable and catastrophic mistake, it's a tool that's too dangerous to use on the daily.
Shift+Del and rm -rf don't have any guardrails around them. In tech you are surrounded by footguns and bear traps. MS made it that much worse by wrapping these in dark patterns that may change without notice but the logic that "dangerous things should be prohibited" is a perfectly good way to end up living in an environment where someone else curates what you can and cannot do. For your protection of course.
A tool isn't dangerous because you can make an unrecoverable and catastrophic mistake (you can make one with a kitchen knife and we still use them every day). It's truly dangerous if it can and does act against your wishes, interests, and reasonable expectations like OneDrive did.
The article is accompanied by a TikTok video I can't scrub through so I can't tell why it's not possible to go to OneDrive's recycle bin and recover the lost data.
Here it is really not a "footgun" that can shoot you accidentally, it is really volontary awful dark patterns.
You say delete my "onedrive" storage content, why on earth someone sane should expect that Microsoft will also delete the data one your computer, that you never asked to be sent to OneDrive in the first place.
The comment I replied to suggested a generalization that "a too that allows you to make grave mistakes is too dangerous to use. We're surrounded by tools in real life and computers which allow you to make major mistakes (ever run a copy/sync tool like robocopy and others with source monitoring, and someone was deleting from the source after seeing the copy at the destination?). So I don't agree with their generalization. Tools aren't dangerous because of what they can do or because they allow you to make mistakes.
But this wasn't a mistake, or at least not an unprovoked one. The user did nothing wrong. They operated under reasonable assumptions established by decades of computer tools. This was a user who didn't get cut by the knife's blade but by its handle. The tool was configured to operate against the user's interests, wishes, and reasonable expectations. This isn't "a dangerous tool" this is a developer who weaponized a tool. The danger is the practice of misleading the user. MS took a pipe and made it a pipe bomb, the solution isn't to declare pipes to dangerous to use.
> why on earth someone sane should expect that Microsoft will also delete the data one your computer, that you never asked to be sent to OneDrive in the first place
From a reasonable user perspective of course it makes no sense. If you investigate from a technical perspective, knowing how the tool works, it "works as intended". OD Backup is not backup, it's storage. That's the first trick MS pulls. OD didn't back up your data, it moved it to the cloud and didn't tell you. This is the second trick MS pulls. Disabling the "backup" means disabling the storage of your single copy of the data. This isn't a trick, it's just the level of competence at MS.
> OD didn't back up your data, it moved it to the cloud and didn't tell you.
Now I think that I understand your mistake. You think that onedrive moves the data to the cloud, and so obviously losing the cloud version makes you lose the file.
But it is not what is happening from my understanding, and here is the very dark pattern:
- The file is and stays in your computer. (Actually OneDrive doesn't know how to store more than what you have in local copy... totally miserable).
- So it is just a "copy" that is sent to the cloud.
- When you delete your files in their cloud (in the sense of getting ride of your storage there, and not only files), only then "OneDrive" actively goes to delete your files in your local disk!
I agree, OneDrive is very similar to `rm -rf`. But I think that is a bad thing for a file sync service to be.
It's worse, because it runs without the users explicit knowledge or consent, and it lacks the implicit guardrails `rm -rf` has (in that most people who use Linux and the terminal are at least literate).
> MS made it that much worse by wrapping these in dark patterns that may change without notice
> It's truly dangerous if it can and does act against your wishes, interests, and reasonable expectations.
Do you really not consider the first to be an example of the second?
> Shift+Del and rm -rf don't have any guardrails around them.
Shift+Del asks for confirmation. I would expect OneDrive to do at least that much before deleting files off the local machine, even if they're recoverable.
> Do you really not consider the first to be an example of the second?
I think too many people got the impression that I'm defending OD and can't get out of that trench. My point is that a generic tool being able to do dangerous things isn't a high enough bar to say don't use it (often). A tool being able to do dangerous things in the manner I described above is a completely different devil. The "how" you end up doing a dangerous thing is what should be punished.
I want to be able to do whatever I want with my computer and my data and not have someone define what's "too dangerous" for me to use. But what happened here wasn't what the users wanted, or could reasonably expect to happen. That's the key.
> Shift+Del asks for confirmation
I'm sure OD also asked for some confirmation. By that time it's too late, you're confirming what you think will happen, not what will actually happen. When you confirm shift+del you know what you are confirming. When you confirm OD's dialog you're confirming under misleading assumptions.
I never asserted that. I asserted that if a tool is that dangerous, it shouldn't be used on a daily basis. I stand by that. Use it if it solves a problem for you, but intentionally every time, not as a matter of habit or in the background with automation.
> It's truly dangerous if it can and does act against your wishes, interests, and reasonable expectations.
> I asserted that if a tool is that dangerous, it shouldn't be used on a daily basis
Agree to disagree. I will repeat, we are surrounded by dangerous tools that we use on a daily basis. Clearly the "danger" part is not the criteria that defines if or how often you should use the tool.
> OneDrive meets those criteria.
Correct. But those are my criteria, and I believe they are the ones that carry my argument. Your criteria was "is dangerous" which is not enough to carry the weight of your conclusion.
Correct, I'm just saying that I think your criteria supports my opinion. As you say, we disagree about this. Fair enough. I'm not telling anyone not to use OneDrive. We all make that sort of decision for ourselves.
All I'm saying is that OneDrive hosed me in a terrible way, so I'm no longer willing to risk using it. Particularly since it doesn't really address any need I have and if I did have such a need, there are better tools (for me) available.
The other dangerous tools you've mentioned haven't ever burned me.
I want to make this very clear, my point is about how we define a “dangerous” tool. It’s not what it can do, it’s how it does it. The real danger is in an untrustworthy tool, in fooling users like OD did.
Options are not a guardrail. Documented options that operate intuitively and consistently are the guardrail.
This is where OD failed by MS's design, it didn't operate intuitively and consistently with almost any other computer tool, and didn't document the behavior properly in a way that the user can take advantage of the knowledge.
> /var for variable data. This is where you would put things like your Postgres data files.
This one never sat well with me. I think of /var as temporary data, something I can lose without much consequence. But never data files. I know it's the default, but still.
/srv I like because it seems like a proper place to separate server-related data, i.e. /srv/wwwroot or similar. But if you like /var, that of course would be the place for this type of data.
No. Temporary data is /var/tmp or /tmp. The difference: /var/tmp should survive a reboot. /tmp might be lost on reboot.
/var is data that needs to be writable (/usr/*, /bin and /lib may be readonly), and that might be important. Like databases, long-term caches, mail and printer queues, etc.
> 3d-cube-SP
> 3D cube rotation benchmark by Simon Speich. The original can be found on Simon's web page. Tests arrays and floating-point math in relatively short-running code.
gives the following results:
Firefox: 305.197
200 First 338.983 Worst 419.309 Average
Safari: 818.449
238.095 First 176.471 Worst 1957.237 Average
which shows that in this particular test, Safari is 2.5 times faster.
Even NT4 handled OOM scenarios better than modern Linux. No, it didn't grind to a halt, it would grind the rust off of the spinning platters. But it would continue to run your applications until the application was finished or you intervened.
Do you have your test harness published somewhere to replicate, i.e. what settings you use for thermals at the UEFI layer as well as OS layer, any scheduler changes you might make, driver versions installed, etc.?
Without knowing exactly how far the common "debloat" Windows tools go, which every computer-toucher seems to recommend, I'd assume the overlap between "Users that disable, intentionally or otherwise, telemetry" and "Users that use 'Right-click -> More Options'" isn't quite a circle - but it is approaching one
reply