Dropbox is safer for syncing because it shows very clearly whether a folder or file is synced or not. iCloud is less reliable in that respect.
Moving projects is easy on a Mac. You simply drag and drop in Finder. From one folder to another folder. But make a sub-folder in your Dropbox folder in case you want to sync with your iOS Scrivener. And make sure that the Dropbox app is running on both Mac:s
To the contrary, we do not have data that would suggest iCloud Drive is unsafe to use. I’m not even sure if the drive optimisation setting is unsafe, given that it is a default (which means nearly everyone using iCloud Drive on Desktop and Documents is using it). Apple has correctly programmed iCloud’s conflict resolution system to handle packages intelligently, so it wouldn’t be surprising if they don’t selectively delete internal component files from packages either.
So my advice would be to not worry about it. You don’t have to go install another service if you don’t want to. Personally I would disable drive optimisation on general principle though, that’s just a dumb setting by Apple. It can lead you into thinking you have physical backups when you don’t.
This isn’t the first time one of the L&L folks have stated that iCloud is probably safe to use for transfer of Scrivener files between Macs, especially if the drive optimization feature is disabled. It’s the transfer with iOS that i gets hazy, as I understand it, because the iOS platform still doesn’t provide enough API access for KB to make sure it’s doing the right thing with the files.
Good to know … closer to my understanding. Me, I’m using Dropbox and getting on with it and not messing around with iCloud at the expense of writing… although looking for excuses as any good author sometimes does!
Yes, it does. I detest this option, for that reason and because it’s a transparent attempt to get people to buy more iCloud space than they need. (Local disk storage is extremely cheap. If you’re running out of room on your Mac, buy an external drive!)
“Optimize Mac Storage” is known to make questionable decisions about what to store locally, leading to the infamous “Binder full of empty files” problem. The function may have improved since it was first introduced, and actual results are going to be very usage dependent: if you have lots of space on your drive and use Scrivener often, you’ll probably be fine. If not, well…