3 ms·

This isn't bad, but why wouldn't you also host the live code on Dropbox as well. One of the biggest bonuses I see about Dropbox is the fact that I am, essentia

This isn't bad, but why wouldn't you also host the live code on Dropbox as well. One of the biggest bonuses I see about Dropbox is the fact that I am, essentially, backed up all the time. If his computer blew up before he hit "push", he wouldn't have a copy. If my computer blows up, as long as I hit save, and Dropbox is synced, I'm good to go. If anything, I'd host my repo somewhere offsite that doesn't use Amazon S3, so that I'm extra backed up.

chipsy 16y ago
If you're pushing around a LOT of files(which I did for a game project's data, the asset compilation process involved several copies and processing) Dropbox can screw up occasionally. If it's just a few source files that you edit in place you're probably fine. Also, some apps may modify files(e.g. a local database) in place without touching their date, which is scary since Dropbox will never update the file until you manually touch it.
instcode 16y ago
Be nice because it hurts Dropbox. I usually save my working source file every small amount of time (quite often) and every single change would create a history version on Dropbox storage server which I don't need that much. I'm not sure how many versions are kept but it is totally a waste of bandwidth as well as storage. So, pick what & when a folder/file to be synced is one of the most key features that I'm waiting for. Yup, cause it's very useful for live projects in Dropbox folder.
- roc 16y ago
  Wouldn't the better solution be for Dropbox to cache those trivial updates to limit bandwidth? It's not as if code is the only thing that might have multiple small updates. Seems an optimization they'd want to solve for themselves, rather than relying on user behavior. And if there's a limit to the version history, isn't the storage concern moot?
fharper1961 16y ago
I am actually storing one of my hg repositories on Dropbox. I don't really see the advantage of having a separate "local" repo. either. I hope I'm not missing something...

chipsy 16y ago

If you're pushing around a LOT of files(which I did for a game project's data, the asset compilation process involved several copies and processing) Dropbox can screw up occasionally. If it's just a few source files that you edit in place you're probably fine. Also, some apps may modify files(e.g. a local database) in place without touching their date, which is scary since Dropbox will never update the file until you manually touch it.

instcode 16y ago

Be nice because it hurts Dropbox. I usually save my working source file every small amount of time (quite often) and every single change would create a history version on Dropbox storage server which I don't need that much. I'm not sure how many versions are kept but it is totally a waste of bandwidth as well as storage. So, pick what & when a folder/file to be synced is one of the most key features that I'm waiting for. Yup, cause it's very useful for live projects in Dropbox folder.

roc 16y ago
Wouldn't the better solution be for Dropbox to cache those trivial updates to limit bandwidth? It's not as if code is the only thing that might have multiple small updates. Seems an optimization they'd want to solve for themselves, rather than relying on user behavior. And if there's a limit to the version history, isn't the storage concern moot?

fharper1961 16y ago

I am actually storing one of my hg repositories on Dropbox. I don't really see the advantage of having a separate "local" repo. either. I hope I'm not missing something...