Git is a second product represented by Linus Toralds ( you might already be familiar with the first one – Linux core ). Staring a discuss about Git, most people will represent its history. Thus, although this system has become extremely popular, not much users are really aware of its benefits and purposes. So, this brief article will help you to jump into Git fairly easy.
I will skip Git installation process and customizing. I will simply advice you to download for Windows, Linux or Mac here and use default settings. If you’re interested in more detailed info, visit official site documentation: for Windows, for Linux or Mac. Use Git quick-start guide to learn more about Git usage.
So, you might wonder if Git is worth using and why so much talks about it. I have found the following advantages of its using:
I will skip Git installation process and customizing. I will simply advice you to download for Windows, Linux or Mac here and use default settings. If you’re interested in more detailed info, visit official site documentation: for Windows, for Linux or Mac. Use Git quick-start guide to learn more about Git usage.
So, you might wonder if Git is worth using and why so much talks about it. I have found the following advantages of its using:
- Distribution: de-centralized management system.
- Branches: every developer that is enabled to commit has his own branch(or even several). He can give it a name of implemented feature. Thus, it will be easy to understand what was done in every branch. Git also has ‘master’ branch where stored application project that is ready for update to production.
- Collaboration: commit changes without distributing others. So, there’s no ‘main’ developer. All of them are equal. There’s no need to wait for other developer’s commit.
- Performance: people think of performance as about time that every branch costs. Well, who cares how much time it will take if you mostly merge files. The real problem is that most of developers(who use other source control management systems) take time for coffee break while merging files. With Git it will take x times less time.
- Reliability: not a single point of failure. If it wasn’t so then no other reason wouldn’t sound seriously. Developers want to trust their data.
- Data view: Whereas other systems look at data as on the list of files, Git thinks of data as of a project. Single file history is mostly uninteresting : developers want to know how a feature - that affects a plenty of files - is implemented. Git history will also show the trace of function if it was transferred from one file to the other.
- Easy to use: basic of Git are easy to understand. The one rule is to forget the way other systems work. And then you will succeed )
- Git is local: the project history is stored locally that result in availability to work off-line.
