4 ms·

If only we could instead have an intuitive version control system which didn’t need crazy explanations or for each team to have a ‘git expert’ who has memorised

If only we could instead have an intuitive version control system which didn’t need crazy explanations or for each team to have a ‘git expert’ who has memorised a few more commands for unbreaking the repo than anyone else. But for now, it seems git is here to stay and many collective hours will be wasted cursing the git who designed it.

jimbob45 5y ago
As a fellow Git-hater, TortoiseGit vastly improved my dealings with Git.
- dan-robertson 5y ago
  Yeah, magit for me. But I feel there ought to be a better way.
- olvy0 5y ago
  Me too, I use TortoiseGit almost exclusively. I have its log view open almost all the time and do all my git actions from there. I can get along in the command line but I'd rather not, my short term memory is awful. I just like seeing the visual feedback of the actions I've just done.
BrandoElFollito 5y ago
I am an amateur dev who, for the last 10 years, is using 3 git commands with fingers crossed (because my only "git expert" is StackOverflow). GitExtensions[1] vastly improved my life. It is a wonderful program. [1] http://gitextensions.github.io/ http://gitextensions.github.io/
na85 5y ago
Git is an awful tool but for most use cases it's much better than CVS, SVN, or perforce or something. I wish the docs weren't so abysmally bad, and I wish it did a better job abstracting away the internals. I don't have time to learn about git's arcane internal shenanigans. I just want version control.
u801e 5y ago
> If only we could instead have an intuitive version control system What makes git any less intuitive compared to svn or cvs? To use either of those or git effectively required reading through documentation to understand what each command did.
- q-rews 5y ago
  I have no experience with those, but the complaint is that there are a myriad of commands and flags and overloads that could basically amount to a handful of common operations and simple resolutions. I myself have “no issues” with git but conflict resolutions are still a guessing game when they’re for middle commits
- seiferteric 5y ago
  Typically git is compared to mercurial which is quite similar in many ways, but feels much simpler. It's been a while since I have used mercurial but I enjoyed it a lot.
- astura 5y ago
  Svn and cvs are centralized, which makes everything much more intuitive and easier to understand IMO. I also think they are simpler (centralization requires less commands)
  - u801e 5y ago
    > Svn and cvs are centralized, which makes everything much more intuitive and easier to understand IMO. For both cvs and svn, creating branches, merging changes from different branches, and switching branches definitely were operations that required a few steps that would not be easy to figure out without reading through the documentation. The only thing that git had that those programs didn't was the concept of a staging area, which, as I understand it, bazaar and mercurial didn't have (unless you created another copy of the repo or another branch to serve as a staging area). But the fact that people have tried to replicate that feature in the other DVCSs indicates that it's a desired feature, even if it does add some complexity compared to not having it.

jimbob45 5y ago

As a fellow Git-hater, TortoiseGit vastly improved my dealings with Git.

dan-robertson 5y ago
Yeah, magit for me. But I feel there ought to be a better way.
olvy0 5y ago
Me too, I use TortoiseGit almost exclusively. I have its log view open almost all the time and do all my git actions from there. I can get along in the command line but I'd rather not, my short term memory is awful. I just like seeing the visual feedback of the actions I've just done.

BrandoElFollito 5y ago

I am an amateur dev who, for the last 10 years, is using 3 git commands with fingers crossed (because my only "git expert" is StackOverflow). GitExtensions[1] vastly improved my life. It is a wonderful program. [1] http://gitextensions.github.io/ http://gitextensions.github.io/

na85 5y ago

Git is an awful tool but for most use cases it's much better than CVS, SVN, or perforce or something. I wish the docs weren't so abysmally bad, and I wish it did a better job abstracting away the internals. I don't have time to learn about git's arcane internal shenanigans. I just want version control.

u801e 5y ago

> If only we could instead have an intuitive version control system What makes git any less intuitive compared to svn or cvs? To use either of those or git effectively required reading through documentation to understand what each command did.

q-rews 5y ago
I have no experience with those, but the complaint is that there are a myriad of commands and flags and overloads that could basically amount to a handful of common operations and simple resolutions. I myself have “no issues” with git but conflict resolutions are still a guessing game when they’re for middle commits
seiferteric 5y ago
Typically git is compared to mercurial which is quite similar in many ways, but feels much simpler. It's been a while since I have used mercurial but I enjoyed it a lot.
astura 5y ago
Svn and cvs are centralized, which makes everything much more intuitive and easier to understand IMO. I also think they are simpler (centralization requires less commands)
- u801e 5y ago
  > Svn and cvs are centralized, which makes everything much more intuitive and easier to understand IMO. For both cvs and svn, creating branches, merging changes from different branches, and switching branches definitely were operations that required a few steps that would not be easy to figure out without reading through the documentation. The only thing that git had that those programs didn't was the concept of a staging area, which, as I understand it, bazaar and mercurial didn't have (unless you created another copy of the repo or another branch to serve as a staging area). But the fact that people have tried to replicate that feature in the other DVCSs indicates that it's a desired feature, even if it does add some complexity compared to not having it.