I guess I'm alone in finding git not that hard to use. My only issue is git isn't pretty and to that end I have a few scripts to give me prettier logs (like most people have) and prettier branch summaries (my macro displays all branches, their latest commit id and dates).
Beyond that I manipulate my tree with straight up git commands.
Any halfway competent developer should be able to master git in a couple of weeks let alone be able to write their own version of git given a couple of full time weeks to work in.
It's just that there's a wider group of people on this forum than one would think.
There are half a million subscribers to this reddit, and a large fraction of them are at the point that they need simple stuff like "Big-O notation" explained to them, while some others are comfortable designing languages that advance the state of the field. There's a continuum between each extreme and we each perceive ourselves as the average.
This doesn't explain it all. The article this thread is about clearly comes from someone who understand Git deeply, yet still complains. To take another example, I know of someone who at some point understood C++98 quite deeply, yet still complained about it.
If the only people who complained about a tool are those who don't know how to use it, the problem is one of ignorance. But when power users complain, we have a strong hint that the problem lies with the tool.
44
u/[deleted] Jun 19 '14
I guess I'm alone in finding git not that hard to use. My only issue is git isn't pretty and to that end I have a few scripts to give me prettier logs (like most people have) and prettier branch summaries (my macro displays all branches, their latest commit id and dates).
Beyond that I manipulate my tree with straight up git commands.
Any halfway competent developer should be able to master git in a couple of weeks let alone be able to write their own version of git given a couple of full time weeks to work in.