4 ms·
It's easy to forget how unintuitive the git model is after you have used it for a long time. It is quite unintuitive. Especially because many use it in conjun
by throwaway_5753 3y ago
It's easy to forget how unintuitive the git model is after you have used it for a long time. It is quite unintuitive. Especially because many use it in conjunction with GitHub which centralizes the decentralized model (and causes impedance mismatches along the way).
But, it does feel like a big upgrade over the past iterations of version control like svn.
- dasil003 3y agoYou’re not wrong, but I think it’s mostly a result of bad porcelain. I did 8 years of CVS and SVN at the beginning of my career, and I remember viscerally how within 6 months I understood the internal behavior of git better than I ever did after nearly a decade of Subversion and predecessor. IMO the git model is an incredibly high power-to-weight ratio for what professional software engineers need, I just can’t get behind efforts to water it down for easier onboarding. No one would suggest professional chefs replace their knives with preformed vegetable slicers from late night TV.
- morelisp 3y agoHow many software developers today are professional chefs (or in training to become one) and how many are unusually high-paying McJobs?
- tasuki 3y agoI'm not entirely sure what "impedance mismatch" means, but am positive it isn't that. GitHub is just another git remote, does not centralise anything, and causes no impedance mismatches.
- karmakaze 3y ago> how unintuitive the git model is This. If new users had the git model itself explained to them, rather than tell them to do their work and learn git as they go (giving them blind commands to type here and there), things would be much better off. It's even more complicated now with github and IDEs having a UI that abstracts over git's abstractions.