3 ms·

What environment are you working in where single-user file sync has the same requirements as a thousand-tenant database? Why do I need atomicity here?

scarface_74 3y ago
Really? If I change 10 files as one logical change. I want to ensure that when I go to the other computer I have all 10 of those changes. DropBox by definition is eventually consistent. You don’t know if all of your changes are synced. That’s not even to mention when I use an automatic refactoring tool that can literally change dozens of files.
- pdntspa 3y ago
  You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. My whole original point to this thread was that the dropbox client can handle tens of thousands of little file changes without breaking a sweat. You could replace text in the entire codebase with one command and it will swallow it all no problem. Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done, but even if you are somehow refactoring your entire codebase every day, the change will be made manifest, and quickly. I don't know if you've ever peeked under the hood of a git repo, but it creates literally thousands upon thousands of tiny little files. Far more than whatever the repo is actually storing. For my uses, where I would run over to a machine and maybe tweak a line or two of code on the laptop and re-run it then return to my desk, there were literally never any problems if I didn't jump the gun (and it was easy to resolve if I did).
  - scarface_74 3y ago
    > You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. And this compares to knowing that when I do a git add/git commit/git push, I know my code is on the server. When I do a git pull, I know my code is on the second computer. > Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done Again, this is literally a problem that git was purpose built to solve and used by millions of developers every day across the industry from the smallest shop up to largest companies.

scarface_74 3y ago

Really? If I change 10 files as one logical change. I want to ensure that when I go to the other computer I have all 10 of those changes. DropBox by definition is eventually consistent. You don’t know if all of your changes are synced. That’s not even to mention when I use an automatic refactoring tool that can literally change dozens of files.

pdntspa 3y ago
You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. My whole original point to this thread was that the dropbox client can handle tens of thousands of little file changes without breaking a sweat. You could replace text in the entire codebase with one command and it will swallow it all no problem. Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done, but even if you are somehow refactoring your entire codebase every day, the change will be made manifest, and quickly. I don't know if you've ever peeked under the hood of a git repo, but it creates literally thousands upon thousands of tiny little files. Far more than whatever the repo is actually storing. For my uses, where I would run over to a machine and maybe tweak a line or two of code on the laptop and re-run it then return to my desk, there were literally never any problems if I didn't jump the gun (and it was easy to resolve if I did).
- scarface_74 3y ago
  > You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. And this compares to knowing that when I do a git add/git commit/git push, I know my code is on the server. When I do a git pull, I know my code is on the second computer. > Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done Again, this is literally a problem that git was purpose built to solve and used by millions of developers every day across the industry from the smallest shop up to largest companies.