When comparing Git for Windows vs tig, the Slant community recommends tig for most people. In the question“What are the best Git clients for Windows?” tig is ranked 5th while Git for Windows is ranked 15th. The most important reason people chose tig is:
If you prefer to do most of your development inside the terminal, changing windows to move to a GUI git client can be annoying. Since tig runs inside the terminal, that's avoided.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro The most powerful way to use git
By using the CLI, one is given access to every single git function available, thus providing complete flexibility in managing git.
Pro Offers three kinds of interfaces
Git for Windows includes a command-line interface in the form of Git BASH, a graphical interface in the form of Git GUI and a context menu interface.
Git BASH offers the complete power of git, Git GUI aims to cover all git functionality (though it falls a bit short) in a graphical way and the context menu enables quick access to simple commands.
Pro Great community support
Since most devs invoke git via CLI, there's a higher chance of getting an answer to a CLI-based git problem than that which is GUI-based.
Pro Can generate an RSA key pair
It's possible to generate an RSA key pair using Git BASH. Instructions on how to do so can be found here.
Pro Gives a better overview of how git functions
By using the git from the command line, it's possible to learn how it functions and how best to get the desired result.
Pro Visual representation of commit-history is possible
Even a visual representation of various branches and how they're merged is possible.
To visualize history:
git log --graph
Pro Allows you to stay in the terminal
If you prefer to do most of your development inside the terminal, changing windows to move to a GUI git client can be annoying. Since tig runs inside the terminal, that's avoided.
Pro Fast
Pro Vim-like bindings
Pro Available in Homebrew
Can easily be installed with homebrew simply by running brew install tig
Pro Works on any platform
Cons
Con Terrible UI
Although it does most of what needs to be done, the actions are not obvious. It is definitely not user-friendly.
Con Steeper barrier to entry as compared to a GUI solution
Since you have to get used to working in the terminal (if you are not already used to doing that) and learn the commands, it has a steeper learning curve than GUI clients which are usually more intuitive and easier to grasp.