Don't ask me because the only SCM I have been using for the past 15 year is git and I hate it. Every company uses it, I made a lot of PowerPoint presentations to teach people how to use it, yet I refuse to use its command-line.
I switched from SourceSafe/SVN/Mercurial to git, but never used Darcs. IMHO git is fine as an assembly language of SCM, but I'm trying to switch to jujutsu which has a better CLI while staying compatible with git as a backend.
My path was cvs -> svn -> arch -> darcs -> hg -> git
I liked arch. I loved darcs, but it blew up on me.
I liked hg, but it was clear that git was going to win, so I capitulated.
Honestly, the worst thing I can say about git is that it's always good enough.
Yes, the CLUI has historically been a dog's breakfast. It seems like some slow improvements are being made, which is great, probably -- I haven't learned them.
But once you get past that mostly-psychological barrier, or if you bypass it completely with a GUI etc, the underlying technology is solid and reliable.
I postulate that VCS is "finished" and that any new tool will need to use git underneath for wide adoption. I hope I'm wrong and someone more creative than I can make me love a VCS again. :)
Comments
Don't ask me because the only SCM I have been using for the past 15 year is git and I hate it. Every company uses it, I made a lot of PowerPoint presentations to teach people how to use it, yet I refuse to use its command-line.
I switched from SourceSafe/SVN/Mercurial to git, but never used Darcs. IMHO git is fine as an assembly language of SCM, but I'm trying to switch to jujutsu which has a better CLI while staying compatible with git as a backend.
My path was cvs -> svn -> arch -> darcs -> hg -> git
I liked arch. I loved darcs, but it blew up on me.
I liked hg, but it was clear that git was going to win, so I capitulated.
Honestly, the worst thing I can say about git is that it's always good enough.
Yes, the CLUI has historically been a dog's breakfast. It seems like some slow improvements are being made, which is great, probably -- I haven't learned them.
But once you get past that mostly-psychological barrier, or if you bypass it completely with a GUI etc, the underlying technology is solid and reliable.
I postulate that VCS is "finished" and that any new tool will need to use git underneath for wide adoption. I hope I'm wrong and someone more creative than I can make me love a VCS again. :)
You may be right, and I think jujutsu or a fork of it is the most likely contender.
I think git is quite nice and easy to work with once you realize one thing: git is first and foremost a filesystem. Version control is built on top.