3 ms·
The interface should be what saves a ton of time, and should not expose the underlying technical model (especially because that model may change at some point)
by bhj 8y ago
The interface should be what saves a ton of time, and should not expose the underlying technical model (especially because that model may change at some point)
- habitue 8y agoI don't think it's reasonable at this point that git's underlying model ever changes substantially. Essentially, it is the interface that's stable over time. It's also the easiest way to understand git. You could learn to read by memorizing the shapes of thousands of words without learning the alphabet or how it matches up to sounds. I'm sure people have done it. But the failure mode when encountering a new word is complete and utter bewilderment that this new shape is unfamiliar, rather than a graceful degradation you get if you understand the alphabet. The same is true of git.
- zaphar 8y agoThis is funny because the lack of consistency in Git's user interface forces you into memorizing the shapes of specific words (commands and arguments). To spell it's language. The UI does a remarkably good job of hiding the elegant underpinnings from you.