Magit vs Git for Windows

Simple tasks, such as commits, can quickly be made without leaving the editor.

Since it's integrated with Emacs, diffs are very easy to fix. You can jump right to any file you want to fix as soon as it comes up in the logs or in the status view.

You can easily learn the mnemonics for the most common tasks and use them to your advantage to speed up your workflow.

In Magit staging a hunk or even just part of a hunk is very easy.

Magit also implements several other "apply variants" in addition to staging and unstaging. For example: you can also discard or reverse a change, or apply it to the working tree.

brew install magit

By using the CLI, one is given access to every single git function available, thus providing complete flexibility in managing git.

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.

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.

It's possible to generate an RSA key pair using Git BASH. Instructions on how to do so can be found here.

By using the git from the command line, it's possible to learn how it functions and how best to get the desired result.

Even a visual representation of various branches and how they're merged is possible.

To visualize history:

git log --graph