Wow, this is just so bad. You're right, stupid is winning.
I learned not to use Dropbox with Git for numerous reason I won't get into here. This was 3 years ago.
Dropbox is not a tool for developers
41–50 of 73 posts
Re: Dropbox is not a tool for developers
#42Lots of posts in here talking about how Dropbox isn't for version control and "just use git" and such, but the systems aren't mutually exclusive and so these comments aren't helpful, IMO. Just because Dropbox isn't a proper version control system doesn't mean it isn't (or couldn't be) useful for developers. I use git daily but I also use a syncing program (first Live Mesh, then Dropbox, now Google Drive) to sync my s…
The only thing Dropbox has over git is the auto-syncing, which will soon no longer be the case ( http://www.kickstarter.com/projects/joeyh/git-annex-assistan... ). 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,…
Did you even read what I wrote?
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.
Re: Dropbox is not a tool for developers
#43I am not sure I understand. I use dropbox with git, but I use the dropbox folder as my origin repository. I initialize a bare repository in my dropbox folder and then push to it from my local working repository. The only time dropbox updates is when I push. I also don't want all of my temporary files replicated anyway and git provides me the ability to control what is and is not in the repository. I hadn't thought to use dropbox as my working directory, but I can imagine that it would be a painful experience.
This is usually only a temporary measure for throw away projects that have potential. When something gets to the point that I am going to deploy it, then I will change the origin to github and push there.
Re: Dropbox is not a tool for developers
#44Earlier quoted context omitted.
Remember remember remember: Dropbox isn't a backup service! Make sure you keep proper backups for your important data.
Dropbox disagrees with you: https://www.dropbox.com/tour/4 Note that I've been using DB successfully as an up-to-the-minute backup since it came out - it's only in the last week I've had problems bad enough to go back to my weekly backups.
Four out of five doctors agree that X is great also. Does it matter what their marketing speak says?
Auto replication to the cloud isn't a proper backup plan, unless you are counting on noticing any missing data within their 30 day backup retention policy (if you are only using their free tier) and restoring your missing data before it is automatically purged.
Re: Dropbox is not a tool for developers
#45I have my local git files saved in my dropbox folder and use git for version control and dropbox to make sure that everything is backed up and on multiple computers at the same time. Doesn't solve the bandwidth problem but unless they are massive changes I think the bandwidth/cpu/memory usage should be very minimal no?
I think the combination of git and dropbox works great.
Re: Dropbox is not a tool for developers
#46Lots of posts in here talking about how Dropbox isn't for version control and "just use git" and such, but the systems aren't mutually exclusive and so these comments aren't helpful, IMO. Just because Dropbox isn't a proper version control system doesn't mean it isn't (or couldn't be) useful for developers. I use git daily but I also use a syncing program (first Live Mesh, then Dropbox, now Google Drive) to sync my s…
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.
Re: Dropbox is not a tool for developers
#47Lots of posts in here talking about how Dropbox isn't for version control and "just use git" and such, but the systems aren't mutually exclusive and so these comments aren't helpful, IMO. Just because Dropbox isn't a proper version control system doesn't mean it isn't (or couldn't be) useful for developers. I use git daily but I also use a syncing program (first Live Mesh, then Dropbox, now Google Drive) to sync my s…
The only thing Dropbox has over git is the auto-syncing, which will soon no longer be the case ( http://www.kickstarter.com/projects/joeyh/git-annex-assistan... ). 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,…
Did you read the comment above you? As a person who bounces around between computers, the syncing part is much more than a "whatever" and, while git-annex-assistant looks cool, it will be some time before I trust it with my most valued documents. Further, niceties like access to code on my iPad, etc, are continued benefits of services like Dropbox.
Re: Dropbox is not a tool for developers
#48This article has very little content for or against their own idea.
What type of developers using DropBox for what?
The only thing I use DB for is for storing/sharing Keepass files and for shared books/resources.
Using it for source code seems wacky to me like a half step above FTP.
Re: Dropbox is not a tool for developers
#49Earlier quoted context omitted.
The only thing Dropbox has over git is the auto-syncing, which will soon no longer be the case ( http://www.kickstarter.com/projects/joeyh/git-annex-assistan... ). 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,…
Did you even read what I wrote? 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.
Yes, they aren't mutually exclusive; but I just don't see the point of Dropbox at all.
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?
Re: Dropbox is not a tool for developers
#50Lots of posts in here talking about how Dropbox isn't for version control and "just use git" and such, but the systems aren't mutually exclusive and so these comments aren't helpful, IMO. Just because Dropbox isn't a proper version control system doesn't mean it isn't (or couldn't be) useful for developers. I use git daily but I also use a syncing program (first Live Mesh, then Dropbox, now Google Drive) to sync my s…
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.
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.