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.
Does Dropbox do merging? Does it track history? Can you run it on server(s) of your choice? Can you setup Dropbox for centralized or distributed operation? Can you inspect the source for security holes? Can you write third party clients, servers, plugins, etc for it?
For once, the headline is perfect: true in every respect and descriptive of the article.
My whole post was based on the premise that using Dropbox (or another similar sync program) and git (or another similar version control system) aren't mutually exclusive. Yet you continue to make it an either/or argument.
Edit: The fact that Dropbox won't merge just seems to me like going backwards, and makes it utterly useless for syncing, IMHO. Since git will merge, and it syncs, why do you need Dropbox?
Edit: sorry for being so tendentious (yes, I like big words :). I'm just really having a hard time "getting" Dropbox as it seems like a poor, closed source replacement for rsync. Git can be used as a glorified rsync that will resolve 90% of multiply edited files, plus it gives you change history, and you're not locked into one company. I understand that git doesn't run on the iPad, but that sounds like a problem with the iPad, not git ;) Git runs fine on not just my Android devices, but my Maemo devices as well.
I keep my source in git, so I get proper versioning, commits, etc.
I keep all my stuff - data files, notes, documentation, agreements, tool installations, ebooks, tools/code made by others in dropbox, so they are the same everywhere.
But the git folders are outside of dropbox. The version control takes care of syncing the code, but there are all kinds of .gitignored files such as IDE path configuration and compiled binaries that differ (and must differ) between my computers. Heck, even most of the code files are different, because their line endings are converted to win or unix style.
I use git daily but I also use a syncing program (first Live Mesh, then Dropbox, now Google Drive) to sync my source code directories. This isn't at all for version control but rather so I can change systems nearly instantly without having to check everything in to a remote git server. This allows me to not care if I'm working on one of my two laptops or my desktop, all my code is Just There whenever I need to switch. With a pure git solution I'd have to push changes that may or may not be a fully coherent change set each time I switched machines.
Anyway, my point is that all of the OP's arguments are still valid when you are using git+dropbox, which is a perfectly reasonable thing to expect to do.
FWIW, all of the major sync systems have issues here (my biggest pet peeve with Live Mesh was that it would hold locks on files for an abnormally long time which would stop me from being able to compile while .o files were being synced, for example). But Dropbox's probably are the most annoying since you have so little control over what does and doesn't sync beyond the root sync directory.