this morning I'm thinking about how git's history of being built as a series of shell scripts has affected its user experience
my sense is
1) a lot of git was originally built as shell scripts
2) the user experience you can provide in a shell script is extremely limited
3) a lot of that now can't change for backwards compatibility reasons
does anyone have examples of this? will talk about how I think this affects merge conflicts in the next post
(1/?)
nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy There's a lot of inconsistency. E.g. a lot of commands are 'git COMMAND VERB SUBJECT', like 'git remote add'. But git tag mysteriously uses flags for its verbs.
nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy part of it can be traced back to the time when collaboration was sending patches via email
nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy
You should interview Linus Torvalds about this. Iām certain he knows a thing or two about the origins of Git. š
nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy
I can think of many examples of #3, but none of them combine that with both #1 and #2, so I'm wondering how similar do you want examples to be?
