Global Feed Post Login
Replying to Avatar Julia Evans

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/?)

Avatar
joachim 1y ago

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.

Reply to this note

Please Login to reply.

Discussion

Avatar
Julia Evans 1y ago

nostr:npub1jdmpcwfd2pf4akk4wrudv48fnfuw5tc3dslsnvxhygd4q85mgcpq4xjwnq that's definitely true, how do you think it's related to those things being shell scripts originally? feels like you could have shell scripts with consistent flags

Thread collapsed