- AWS Automation Cookbook
- Nikit Swaraj
- 250字
- 2021-07-02 23:00:37
Why Git over other VCSs?
It wouldn't be appropriate to say Git is better than SVN or any other VCS. It depends on the scenario and the requirements of the project. But nowadays, most enterprises have chosen Git as their VCS for the following reasons:
- Distributed nature: Git has been designed as a distributed VCS, which means every user can have a complete copy of the repository data stored locally, so they can access the file history extremely fast. It also allows full functionality when the user is not connected to the network, whereas in a centralized VCS, such as SVN, only the central repository has the complete history. This means the user needs to connect with the network to access the history from the central repository.
- Branch handling: This is one of the major differences. Git has built-in support for branches and strongly encourages developers to use them, whereas SVN can also have branches, but its practice and workflow does not have the inside command. In Git, we can have multiple branches of a repository, and in each repository, you can carry out development, test it, and then merge, and it's in a tree fashion. In SVN, everything is linear; whenever you add, delete, or modify any file, the revision will just increment by one. Even if you roll back some changes in SVN, it will be considered a new revision:
- Smaller space requirements: Git repositories and working directory sizes are very small in comparison with SVN.
推薦閱讀
- 繪制進程圖:可視化D++語言(第1冊)
- PowerShell 3.0 Advanced Administration Handbook
- Python Artificial Intelligence Projects for Beginners
- CSS全程指南
- 條碼技術及應用
- Expert AWS Development
- MicroPython Projects
- 小型電動機實用設計手冊
- CorelDRAW X4中文版平面設計50例
- AWS Administration Cookbook
- The Python Workshop
- Citrix? XenDesktop? 7 Cookbook
- The DevOps 2.1 Toolkit:Docker Swarm
- SQL Server數據庫應用基礎(第2版)
- 會聲會影X4中文版從入門到精通