The Mac numbers don't surprise me at all, as the large influx of unix people to the platform are more used to using CLI tools.
(yes, I'm saying that on the whole, Mac users are less afraid of the CLI than Windows users. Shocker!)
The Mac numbers don't surprise me at all, as the large influx of unix people to the platform are more used to using CLI tools.
(yes, I'm saying that on the whole, Mac users are less afraid of the CLI than Windows users. Shocker!)
I disagree with the blanket statement about Mac users. Developers using Mac are not Mac users by a long shot. For most of us I know it is a case of the Mac being a better *nix dev box than the alternatives.
But when switching to Mercurial, the gui tools weren't as good, so I learned how to use it via the command line. And, to my surprise, I found that it's much easier to use the command-line rather than the gui tools. Everything goes much faster.
So if you're a Windows dev, like me, and have never tried solely using the command-line tools before, I suggest you give it a shot. You may be surprised like I was.
(I DO think this means there's a great deal of potential profit available to someone who releases a GREAT git gui for OS X)
Personally, I use vimdiff.
What is it you'd want from a "Great Git GUI"?
You can't use Git completely without a GUI [1] and not having everything in a GUI means I'm forever typing some command and then typing another command (or several) to make sure what I expect is actually what happened. To "visualize", if you will. In a GUI I could just see it and this would save a lot of time.
[1] Diffs are visual (vi is a GUI). I'm sure some clown will show how it's possible to use ed or something so you can really do everything without a GUI, but the effort that will take demonstrates my point nicely.