> They're always renaming and moving files and folders to keep things organized. Ah, there we go! It's their won fault for assuming a filesystem can be used f

> They're always renaming and moving files and folders to keep things organized. Ah, there we go! It's their won fault for assuming a filesystem can be used for basic file and folder changes. /s On a serious note, it turns out that replicated filesystems as seen in OneDrive or DropBox are hard to engineer. Astonishingly difficult to get right. "Formal proof verifiers" level of difficult, otherwise customers will lose data in everyday circumstances. It's happened to me, it happened to all of my coworkers, and it has happened to your customers. Data loss with a poorly engineered replication system isn't some rare corner-case, it's the typical case, and it is a miracle if data isn't lost! A few years ago DropBox rewrote their sync engine and wrote a great blog article about all the complex scenarios they had to handle: https://dropbox.tech/infrastructure/rewriting-the-heart-of-our-sync-engine https://dropbox.tech/infrastructure/rewriting-the-heart-of-o... The OneDrive team has done none of this hard work, I guarantee it. OneDrive loses data if you look at it wrong. If you call Microsoft Support they'll tell you not to look at it like that. Or they tell you to go complain on some support forum, as-if that's the industry standard for achieving engineering rigour. I do all of my work on local C:\ paths and copy files to SharePoint or OneDrive only if forced to collaborate with colleagues. This rare interaction with OneDrive causes data loss about 5% of the time, often enough that I notice.