All this talk of efficiency, yet the Dropbox windows client is such a bloated multi-process memory hog of a mess that I ended up uninstalling it and rigging my own sync with a command line tool (dbxcli), with about 1000x less resource usage. For all this attention to saving their server's resources they sure don't seem to care much about wasting their customers'.
This is classic. "We spent $x million developing a compression algorithm in Rust to slightly speed up a background process in our bloated Electron app!"
Broccoli: Syncing faster by syncing less (2020)
21–25 of 25 posts
Re: Broccoli: Syncing faster by syncing less (2020)
#22Re: Broccoli: Syncing faster by syncing less (2020)
#23Earlier quoted context omitted.
This is classic. "We spent $x million developing a compression algorithm in Rust to slightly speed up a background process in our bloated Electron app!"
The Electron app wouldn't be an issue if it didn't churn away uselessly even when Dropbox is in the background. The company doesn't care though, their advice was to open a topic in the support forum, to which their response is "This idea will need some more support before we can share it with the team." You can lead a horse to water.
When I told the support person that this was a problem, he flat out refused to open a ticket or file a bug report. He denied that this was a problem!
That was a couple of years ago, so maybe they have improved since then, but I'll never find out.
Re: Broccoli: Syncing faster by syncing less (2020)
#24Re: Broccoli: Syncing faster by syncing less (2020)
#25I really wish this idea had become more widespread. Microsoft Research published this 15 years ago. It shipped as part of windows but the paper describes it in enough detail to implement it I think. I got it running years ago and it seemed to work really well. https://www.microsoft.com/en-us/research/wp-content/uploads/...