> there's that one coworker who knows a bit more about Git than everyone else, who helps get us back on track whenever our local repos end up in a strange state
every single article about git comments on this "feature" of git...isnt it time we all removed the aura of geniousness to git and bloody moved on to something better?, (like svn for instance)
I cannot imagine how learning a new version control system would make me more effective. Git stays out of my way 99.9% of the time, and the last 0.1% gets resolved after a few minutes of googling, reading docs, or asking chatgpt.
- the individual opportunity costs of learning multiple VCSs likely outweigh the cost of learning 1, even if it's suboptimally difficult
- the community-wide leverage lost by having significant fractions of prospective oss devs who aren't comfortable contributing via one VCS or another probably outweighs the marginal leverage lost by alienating the fraction of prospective oss developers that find git unlearnable or oppressive or whatnot
(I am ~fine with breaking the monoculture for a once-a-generation move to a clearly superior model, but there's a risk of fracturing the ecosystem across several VCSs for decades to come.)
Perforce is used in game dev since it handles binary files super well, and is used by many people who aren't engineers. It's not perfect, but it's super easy to use and the GUI tooling is amazing.
I've used Perforce before moving to Git (and used rc and svn before that), everyone has had the same issues with one team member knowing it better and being to go to person for resolving issue. With Perforce the GUI is okay, or at least it was 10 years ago when I was using it, but we always went to the cli interface for many things not supported in the GUI. A GUI can't cover every option and be usable. Visual metaphors are more accessible initially but eventually they become overwhelmed and you need to move to linguistic metaphors like the cli and code.
I cringe everytime I'm forced to use perforce for work. Every action is more convoluted, slow and painful compared to git. Perforce might be great for binary files and non-technical users. But there is absolutely no reason to choose it over git when working with source code.
I started with CVS, and it made complete sense to me. Git isn't bad, but it's what I use these days.
For some reason, I never grokked svn. Something about the use of directories as versions always threw me for a loop. Maybe if I spent the time to really learn it I'd like it, but that isn't likely to happen these days.
Subversion didn't use directories as versions, it used them for branches. For versions, subversion is like using git with a monorepo. Every commit is a new version across the whole repository.
It was a simple and clever design but it's hard to argue for it when compared distributed nature of git and its ubiquity.
every single article about git comments on this "feature" of git...isnt it time we all removed the aura of geniousness to git and bloody moved on to something better?, (like svn for instance)