ismarc 6 minutes ago | link

This has been the opposite from my experience with Scala. Rather than build a single system with a large codebase, it allows us to build small, compartmentalized systems and compose them together. Then again, we don't use maven, instead using ant for building and git submodules to handle dependencies.

First the short version: I use git-add -p frequently, and git-commit -a almost never

Preston-Werner’s bet has paid off. GitHub is now profitable. Users can sign up for free and start contributing, but they pay money if they want to privately host code there — starting at $7 per month. GitHub also sells an enterprise product that lets companies run your own version of GitHub behind the corporate firewall. That starts at $5,000 per year, but can cost hundreds of thousands annually for companies with hundreds of coders.
...
When Scott Chabon wrote a book about GitHub, the first fork appeared within a month. It was a German translation of his book. Now, three years later, it’s been translated into 10 languages, with another 10 translations in the works. Half of the traffic to the book’s website comes from China. “Tons of people in China are learning Git because they can read [the book] in Chinese on my website, because somebody provided that,” he says

25 points by andywhite37 3 hours ago | link

I think Git owes a ton of its success to github.com. Without this extremely well-designed, central repository for repositories, the uptake of Git would have been much slower, and faced much more resistance in the wild. Git is a great tool on its own, but having a centralized place for people to learn and use Git has been huge.

reply


5 points by beagle3 2 hours ago | link

apenwarr's own "bup" http://github.com/apenwarr/bup - it's the ultimate backup system on one hand, and it's just a git repository on the other.

Way better deduplication than any other backup system you've used, every backup is at the same time incremental, differential and (looks) complete.

It's magic.

Dropbox is a free file synchronization/backup service where you can backup, save and share files. One of the best things is, that you can use it as git server.

Here is an example on how to do it. To start, open a shell/terminal window and go to your project directory:

The Parable

Imagine that you have a computer that has nothing on it but a text editor and a few file system commands. Now imagine that you have decided to write a large software program on this system. Because you’re a responsible software developer, you decide that you need to invent some sort of method for keeping track of versions of your software so that you can retrieve code that you previously changed or deleted. What follows is a story about how you might design one such version control system (VCS) and the reasoning behind those design choices.

27 points by msy 4 hours ago | link

Thing is, while both Ruby & Vim have been driven by what she's describing she neatly sidestepped why those movements got started in the first place. Ruby gained huge traction primarily via Rails because working on PHP is unenjoyable to many and Ruby is a really pleasant language to work with. Vim's recent resurgence can largely be traced to development of Textmate grinding to a complete halt. Textmate's rise a few years ago was due to BBEdit failing to evolve. Git beats seven shades of shit out of SVN. Erlang provides a proven answer to concurrency issues. Javascript is the only choice for the ever more important front-end side of web development. Each of these shifts of development momentum have rational, logical underpinnings.

10 points by mdwrigh2 8 hours ago | link

The main point of creating his resume with Markdown seems to be the ability to store it in version control, and hold the whole thing in a plain text file. While a resume done in Markdown seems like an interesting idea (and I may end up writing one up just to have a web version of it online), I'd also consider writing one in LaTeX. It's easily storable in version control, and the base file you use to generate the PDF is a plaintext document, which is exactly what he's looking for, and the system is a lot more flexible than Markdown.

As an example, my resume can be found at https://github.com/mdwrigh2/resume/raw/master/mwright-resume... and the source for it can be found at https://github.com/mdwrigh2/resume/blob/master/mwright-resum...

About a month ago, I published a series of articles on Git, starting with @nvie’s awesome git-flow and asking you to write better commit messages. The series ended with an article named “The mighty reflog and the amazing bisect”. Guess what? I forgot the magical rebase.

!!!

5 points by epall 6 hours ago | link

Biggest plus for me:

"git checkout A...B" is a way to detach HEAD at the merge base between A and B.

I always find myself trying to figure out where two branches meet in the history.

reply



3 points by oomkiller 6 hours ago | link

Homebrew for OS X already has a new package for 1.7.0. Just run "homebrew update" and "homebrew install git"

Linus Torvalds on rebasing:
* http://kerneltrap.org/Linux/Git_Management
* http://lwn.net/Articles/291302/
* http://lwn.net/Articles/291303/
* http://lwn.net/Articles/291304/

Matt Mackall on synchronizing (pull + merge, don’t push, don’t rebase):
* http://www.selenic.com/pipermail/mercurial/2008-July/020116.html
* http://www.selenic.com/pipermail/mercurial/2008-July/020131.html

A fast, powerful backup system built upon Git and efficient, compact tools written in OCaml (faster than the C counterpart with 1/5th of the code :)