3 ms·
I'd like to take this post out of context and comment on the HN-submitted title alone. For me, it perfectly describes what i love about git and what i hate abou
by skrebbel 14y ago
I'd like to take this post out of context and comment on the HN-submitted title alone. For me, it perfectly describes what i love about git and what i hate about git.
Git is indeed an editor, but it's like edlin.
It's not Vim or Textmate or Excel. I want a Git that works like an editor, not requiring me to keep in my head (or in some shell bells and whistles) 'where i am', and what I can or should do now. Not a UI frontend with buttons for single-shot editing commands, but a real editor, that makes use of 2-dimensional space, to somehow really edit everything that matters to me about versions and sharing and changes and all that.
It's a really powerful metaphor. Microsoft did something very right when they released Windows Explorer with Win95, which treats your harddrive like it's a document that you're editing (i bet it's a ripoff, but that's not the point here). Copy, paste, undo, it's all there.
Can't we design something similar for distributed version control? How well would document-editing metaphors map to git? My underbelly feeling says that it might be a surprisingly good match, given the right visualization and editing primitives.
- saraid216 14y agoWell, in lieu of a really thoughtful response, let me ask this: If Git is an editor, the obvious question is... what is it editing? I'm guessing that the answer is "history", but that's fuzzy to me and I'd have to think some more for a better answer.
- pekk 14y agoThe analogy with an editor seems weak to me, since pushed history shouldn't change. But you are editing something like a tree of patches (changesets).