points by martheen 2 days ago | 0 comments
In Windows, by default, Microsoft tools put projects in ~/source/repos, which OneDrive, in turn, by default won't touch so they'll be lost if the SSD fail and they're not in git.
However, OneDrive doesn't seem to even know how to handle source files (it doesn't even attempt to honor the gitignore), so rebuilding a project in folders covered by OneDrive results in flurries of temporary files being uploaded/updated to the cloud, hogging the bandwidth, with a bonus of locking files, crashing builds, or even reverting changes silently.
One would think backup tools, even if primarily for normal users are still literally made by programmers, at least consider the use case of programmers instead of just ignoring them entirely.
[–] ihateolives 2 days ago
[–] KPGv2 1 day ago
file sync is backup against the things most people have to deal with (hardware breaking, theft, house fire, residential lightning strike)
[–] BSDobelix 1 day ago
I would say accidentally deleting a file is more common than a house fire, so NO, file-sync is not a backup nor is RAID (block-sync) or clustering (data/state-sync).
A backup is/should be a non-modifiable snapshot of data/files maybe even a state.
I give you an example:
You have a password-safe (as a file). Your computer blows up, but you are safe, because your password-safe is synced on Dropbox....but oh my god what was the password to Dropbox??? Your restore is gone because you forgot to "backup" your password-safe.
However you are not a Loser, being a Admin is a ~lost art and a really good paid one (again).... ;)
[–] KPGv2 1 day ago
It goes to your trash can/recycle bin for a while. That's literally what it's for: to guard against accidental deletes. Very few people accidentally delete files from their computer's drive anymore. The only time people do this in 2026 is accidentally formatting an SD card that had their camera's pictures on it or something.