[lojack]

That may work for the lone developer, but what happens when you're on a team with shared Dropbox folders, all working on the same code base concurrently. I understand your reasoning, and I'm not trying to say you are incorrect in doing this as it's a very legitimate use case. It is, however, important to understand that using Dropbox in this way, in the context of syncing the git repo for teams, is a step backwards.

[georgemcbay]

It makes no difference if I'm working alone or on a team. Syncing locally changes nothing about my source code control usage. I'm still pushing my changes into a shared repo (on a remote server) when it is time to do that, but since I'm syncing locally (including my .git directory usually) I can push from any one of three different machines, whichever I happen to be working on when it is time to do the push.

[lojack]

I understand this, which is why I specifically said it wasn't wrong. Just saying that serious issues could arise when a less experienced developer shares their Dropbox folder and others treat that folder as their own clone of the repository. This should never happen because we know better, but the realist in me says its inevitably going to happen at some point.

[georgemcbay]

Yeah that's a potential problem if people are doing that. I certainly don't recommend sharing a repo directory among multiple people via Dropbox.

I don't share my sync folders publicly at all, they exist only for my own convenience when it comes to switching between different systems as needed.

[SoftwareMaven]

He's not talking about syncing a git repo for multiple developers with it. He's talking about syncing his work with it. Of course it's not a replacement for a centralized git repo.