Re:How we rolled out one of the largest Python 3 migrations
by PurpleRamen on Wednesday September 26, 2018 @02:22AM
(#18073206)
I don't think there is much code for conflict-resolving in dropbox. Usually in case of conflicts it renames one of the involved files and add a message about conflict and the date to the name and moves on.
Re:How we rolled out one of the largest Python 3 migrations
by varenc on Friday September 28, 2018 @06:58PM
(#18097721)
Perhaps there's lots of code to minimize the number of times a real conflict occurs?
Re:How we rolled out one of the largest Python 3 migrations
by thijsvandien on Tuesday September 25, 2018 @06:44PM
(#18071183)
I agree that syncing is far from trivial, but that doesn't change it's a single purpose.
Re:How we rolled out one of the largest Python 3 migrations
by kiriakasis on Tuesday September 25, 2018 @07:13PM
(#18071354)
Not to build a straw man but by this logic also a browser is a single purpose application
Re:How we rolled out one of the largest Python 3 migrations
by paulddraper on Tuesday September 25, 2018 @07:36PM
(#18071477)
A rocket ship is also "single purpose."
Watching files. Keeping backup of files. Keeping conflicts resolved. Watching Selective Sync files and folders. Watching Smart Sync files and folders. Notifications for synced files. Etc. etc.
There’s way more the client does than what I mention.