「结构」「原理」「细节」「枯燥乏味」

这是从楼主的原话中挖出来的几个词语，碰巧的是，恰好是区分普通码农和优秀序员的关键词。

过来人表示不要紧，很快你就习惯了

Yeah, 又找出一群能 ban 的人
@rankjie 废话，当然不用，这还用说么？

看在楼主是妹纸的份上我就呵呵而过就算了

这年头还去兼容 IE6 的网站才应该被批判，请楼主与时俱进。

Smaller Space Requirements

Git's repository and working directory sizes are extremely small when compared to SVN.

For example the Mozilla repository is reported to be almost 12 Gb when stored in SVN using the fsfs backend. Previously, the fsfs backend also required over 240,000 files in one directory to record all 240,000 commits made over the 10 year project history. This was fixed in SVN 1.5, where every 1000 revisions are placed in a separate directory. The exact same history is stored in Git by only two files totaling just over 420 Mb. This means that SVN requires 30x the disk space to store the same history.

One of the reasons for the smaller repo size is that an SVN working directory always contains two copies of each file: one for the user to actually work with and another hidden in .svn/ to aid operations such as status, diff and commit. In contrast a Git working directory requires only one small index file that stores about 100 bytes of data per tracked file. On projects with a large number of files this can be a substantial difference in the disk space required per working copy.

As a full Git clone is often smaller than a full checkout, Git working directories (including the repositories) are typically smaller than the corresponding SVN working directories. There are even ways in Git to share one repository across many working directories, but in contrast to SVN, this requires the working directories to be colocated.

当不能决定学什么语言的时候，就学 JS

Guido 白瞎了

好一个楷体字

云存储不精明，楼主才精明

只要别自动播放就行

mysql -h localhost -u <USERNAME> -p="<PASSWORD>" -D <DATABASE> -e "show databases;show databases;show databases"