> I know Burcu Dogan was against automatic sync because it isn't 100% reliable in every case, but frankly she's wrong. That isn't a sufficiently bad con not to use it compared to the pro - it's automatic.

With a bit of bad luck, automatic sync easily turns into a mess (see the trainwreck that is Apple Music; even the most devoted fanboys loathe it).

With big enough amount of bad luck, anything can turns into a mess. OTOH sync (two-way sync) if done right can work pretty well and is quite useful in the real world. I am saying it as the developer of Autosync for Google Drive android app (https://play.google.com/store/apps/details?id=com.ttxapps.dr...)

I appreciate that it's starting to get off topic, but in my experience the problems with Apple Music isn't related to whether the sync is automatic or not.

The issues that I run into are UX issues (not sync related), and what I've heard is problems with what the server does once a sync is finished (automatic or not).

Personally, I prefer manual sync like Burcu does. You have way better control with manual sync, imagine you were editing a video or had source code in your drive that was shared, any saves would toggle syncing. Also you could potentially clog up your bandwidth with auto syncing. Plus I can get to review a manifest of files before letting them get pushed. Lots of other features with manual sync such as `cat pipe | drive push --piped streamedContent` or `drive push -m ~/contentNotInDrive .` and many others. These would be very difficult to get in with auto-sync.

I like the approach drive takes, but if you are looking for full automatic sync, there is also InSync https://www.insynchq.com/ (linux client available; I've installed it from the AUR for example).