I agree but it's easy to forget the premises on which it makes sense.
I like the idea of storing my git bare repository on my dropbox, while pulling from it to another non-dropbox directory. For a private repository, it's a nice alternative to using bitbucket. But, I think it is only reasonable if I'm the only one syncing with the repository. As soon as I want to collaborate on my shared private git repo, time to use bitbucket.
With Logic Pro, I will record directly into Dropbox, but only if I turn off sync while recording. Then I can share the project with my mixer/editor in another state. But there again we make sure not to be in the project at the same time.
In short, my sense is that Dropbox is for sync and backup. It's not for simultaneous co-working.
For those who don't click through, the linked SO answer recommends using Dropbox to sync a "remote" repo between your computers, and push/pulling that from your working repo outside of Dropbox.
I like the idea of storing my git bare repository on my dropbox, while pulling from it to another non-dropbox directory. For a private repository, it's a nice alternative to using bitbucket. But, I think it is only reasonable if I'm the only one syncing with the repository. As soon as I want to collaborate on my shared private git repo, time to use bitbucket.
With Logic Pro, I will record directly into Dropbox, but only if I turn off sync while recording. Then I can share the project with my mixer/editor in another state. But there again we make sure not to be in the project at the same time.
In short, my sense is that Dropbox is for sync and backup. It's not for simultaneous co-working.