News for hackers. Stuff that matters.
Re:Dropbox will kill your insane MacBook Air 2013 battery by jwr on Wednesday July 03, 2013 @07:25AM (#5983775)
I do use git. But I often develop on two machines: a laptop and a Mac Pro. Which means I am often in the middle of something when I have to just pick up the laptop and go. "In the middle of something" means that just pushing commits over doesn't cut it. I can (and do) rsync stuff over, but that is annoying and very error-prone (it's too easy to sync stuff the other way around and lose work).

I guess you could say Dropbox gives me finer sync granularity than git does.

Dropbox seems like a perfect solution: have a single place where you keep code, develop on two machines, just pick up your laptop and leave whenever you want, without worrying about sync.

Re:Dropbox will kill your insane MacBook Air 2013 battery by timtadh on Wednesday July 03, 2013 @07:55AM (#5983889)
I don't understand. You can easily cut a branch commit. Push the branch. Pull the branch finish it. Commit. (optionally rebase). Delete the temporary branch. Git handles this problem very well.
Re:Dropbox will kill your insane MacBook Air 2013 battery by jwr on Wednesday July 03, 2013 @08:24AM (#5984026)
Right. I get a call, I need to leave for a meeting in 5 minutes. This is exactly the time when I want to cut branch commits, push branches, pull branches, commit and rebase. Even rsync is better than that.

Put it another way, I don't understand why you'd use Dropbox at all, after all you could easily version all your files in git, using push/pull/branch/commit/rebase to get your data to your different machines. Git handles this problem very well, after all.

Re:Dropbox will kill your insane MacBook Air 2013 battery by snowwrestler on Wednesday July 03, 2013 @10:57AM (#5984922)
The specific problem with git in Dropbox is that working in git can cause a large number of transient files changes as you, for example, switch branches. Dropbox doesn't know those are transient changes and attempts to sync all of them. That is one reason it can drain battery so fast.

Obviously with regular files, that is not an issue, so Dropbox works well. (unless you're managing them with git, I guess)

If you're willing to accept the "lightness" of git branching and commits, it's possible to "save and sync" your work very quickly. Assuming you're on a dev branch:

git add -A

git commit -m "temp commit 2013-7-3"

git push origin

You can even script this, see for example:

http://stackoverflow.com/questions/8482843/git-commit-bash-s...

Then when you're ready to work on a different machine, you fetch from origin.

If you want to keep your commits meaningful on your dev branch, you can create a temp branch first, then rebase later to get rid of the ugly temp commit.

git checkout -b temp123

Re:Dropbox will kill your insane MacBook Air 2013 battery by timtadh on Wednesday July 03, 2013 @10:26AM (#5984698)
I don't use dropbox at all? To me it is a great solution for consumers but my needs are different. I use git + standard unix tools. For backup I use tarsnap. It rocks.
Re:Dropbox will kill your insane MacBook Air 2013 battery by jasonlotito on Wednesday July 03, 2013 @08:06AM (#5983944)
You don't understand or you didn't spend ti e thinking about that. It's doing all those steps, or doing nothing and achieving the same result. Not sure what you don't understand.
Re:Dropbox will kill your insane MacBook Air 2013 battery by StavrosK on Wednesday July 03, 2013 @08:01AM (#5983919)
My use case: The "extras" (files not in the DVCS like libraries, dependencies, etc) are just as important for working, but they take too long to transfer/update from one PC to the other, especially for things like GAE which don't have easy ways to manage.

Dropbox could help there, but it does not.