2 ms·
Part of why I like git is the lack of abstraction. Lack of abstraction means the abstraction that isn't there can't leak. I've done some bizarre things in git,
by jerf 15y ago
Part of why I like git is the lack of abstraction. Lack of abstraction means the abstraction that isn't there can't leak. I've done some bizarre things in git, mostly induced by the fact the company I'm working for is still on SVN in the core. For instance, on two fundamentally different machines based on the same source tree, I developed a shared feature on one, bundled it all up into one commit, put some work into integrating it on the other, put some more work on the original and bundled it up into one new unified commit, pulled from the second machine and did an interactive rebase to slide the new megacommit under the integration commits. And it all worked perfectly and exactly as I expected, complete with dead-on accurate merge conflicts that truly were conflicts. If you had problems following that description, well, git didn't.
Yes, to the extent that may seem like a bizarre workflow, it is. I know. There are additional constraints I did not describe. The point is, it's a workflow that git doesn't close off with leaky or over-limiting abstractions.
That said, I totally agree that this is irreducibly a strength and a weakness at the same time, and YMWV. But I'm glad it's around so I can use it. It's saved my bacon more times than I can count.
- dogweather 15y agoFor sure, it's nice to have both available: high level and low level. Like Ubunutu's user-add and add-user. (Of course, those are horribly named.)
- platz 15y agoIn other words, perhaps git is like C