4 ms·

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 wa

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 https://github.com/jesseduffield/lazygit

thewakalix 5y ago
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.
- RodgerTheGreat 5y ago
  perhaps you have heard of BANCStar: https://esolangs.org/wiki/BANCStar https://esolangs.org/wiki/BANCStar
- deleted 5y ago
  [deleted]
SilverRed 5y ago
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.