3 ms·
It's not just a leaky abstraction, there is no abstraction! It's the opposite of user-centric design, like a car with no body where you adjust the gasoline pum
by jollybean 5y ago
It's not just a leaky abstraction, there is no abstraction!
It's the opposite of user-centric design, like a car with no body where you adjust the gasoline pump, the transmission, the amount of oil etc. yourself.
There's an underlying model, which is tricky but not rocket science - and all actions on that model can have a bunch of non-obvious state changes and side-effects.
It's just complicated enough that it's hard to keep track of the models+statefullness without some expertise, experience and thought.
The first time I saw an 'animation' of what was going on with various commands, it blew my mind how much I learned as I saw things happening.
The language we uses is often not very specific and leaves out important details.
We use it because there's a kind of simple brilliance to the underlying model, it's very fast, very robust, and works well for open source.
That said, I wish there was a git optimized for teams and with better abstraction.