Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it. After 1 year of git experience I could trivially do things that I never would have even attempted after a decade of CVS and SVN.

> Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it.

One of these years I'll be comfortable with git. Maybe next decade.

This helped me learn git visually.

https://learngitbranching.js.org/

You can probably complete that in less than a day

Make yourself your own git cheatsheet of what you need, and maintain it with examples from usage. It'll click in place and be useful.

have my own cheat sheet. it still hasn't clicked.

I Just copy blindly off the cheat sheet.

hopefully something better will come along.

But you get your job done? Git's just another tool. My guess is you've got bigger fish to fry.

Exactly. Anyone is free to continue using subversion but collectively we have decided the learning curve of got is worth the flexibility.

AFAIK git was initially built to be a source control engine for other tools to build on top of, but most people have just used the underlying engine since it was easier. But I've really started to grok git after using a program called lazygit [0]. Basically a terminal UI on top of git where I don't have to remember the messy language of the engine, I just need to remember a couple of keystrokes.

[0] https://github.com/jesseduffield/lazygit

There are loads of UI layers over git. But largely the git cli is just better and more logical. Other than some minor weirdness, its a pretty good tool.

The GUIs never expose the full power or standard error messages that the CLI will. Had a case where gitlab was blocking a push because the master branch was protected. The git gui gave the wrong error message about why the push was rejected.

Reminds me of how Lisp’s syntax was meant to be an intermediate format, but everyone found it intuitive enough that they didn’t bother writing the planned non-sexpr language.

perhaps you have heard of BANCStar: https://esolangs.org/wiki/BANCStar