4 ms·
First, it is not a browser. You actually do commits, merges and manipulate branches. The size is that big because Gitbox is bundled with official Git binaries
by oleganza 16y ago
First, it is not a browser. You actually do commits, merges and manipulate branches.
The size is that big because Gitbox is bundled with official Git binaries so you don't have to install anything else. I will see how to bring the size down in the next versions. Anyway, this fact does not affect the performance and does not eat much memory.
- to 16y agoso is that better than gitx?
- oleganza 16y agoGitbox is better because it is a pleasure to use. There are tons of little details which matter in a daily work. For instance, when you switch a branch and try to commit to it, the branch name will be highlighted to remind you that the branch was switched since last commit. If you forgot to switch back, you just cancel the prompt. This little thing instantly eliminates 50% of use cases for "git reset --hard" or "git cherry pick" and makes you happier. Also, Gitbox fetches remote commits automatically so see that you have to pull something: this eliminates unnecessary merge commits.
- mxcl 16y agoI'll be sure to give it a thorough testing. Thanks for your work.
- dabeeeenster 16y agoThanks for the reply - I'm always suspicious of large binaries with OSX!
- pornel 16y agogit-osx-installer package takes 4.3MB, but your git.bundle takes 150MB. The problem is that the bundle contains exactly same binary 104 times (git, git-add, git-apply, etc. are identical files, 1.3MB each). These should be symlinks. It might be ZIP's fault (doesn't support symlinks AFAIK). I distribute my apps as tar.bz2, and nobody complained yet.