| Git already has layers on top of it like git porcelain or the various GUI tools that attempt to handle things smoothly. > significant time and energy All someone needs is to read through https://rogerdudler.github.io/git-guide/, and learn a few commands. Are we seriously going to refer to “reading the manual” as “significant time and energy”? In this case you don’t even have to read the manual, just a primer on how git works. You know, on how the tool that you’re using works. Why are people so allergic to spending even a modicum of time on learning a tool that massively simplifies their life and makes their work possible? Do plumbers complain about having to read manuals for the equipment that they use? Electricians? As programmers our tools are easier to learn and use, yet we complain about having to any work at all. Why even be a programmer? If reading about git is so hard, what about the rest of the field that doesn’t even have documentation? How about we don’t make tools that cater to the lowest common denominator, in this case people who basically can’t be assed to do anything? RTFM. |
I have a way of picking the losing side so I've been using mercurial for everything until now, and until now Bitbucket offered hg. They're decommissioning it so I'm moving over to git and I feel like my workflow has been hampered, not just in the immediate complexity of learning the new tool, but in the ongoing complexity of using a less good tool for my needs.
I'm dealing with it, but the situation you're describing isn't really the one that I and a lot of other whiners are dealing with.