Nostr Web Client

joachim

53f711b63a87f78be97e15d5d4e900ce7bde8da55b23586425d5bf4a16aed2c9

'Jaz dood' - my 6yo. I mostly post about programming, politics, cycling, and random things that amuse me.

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:npub16l6vecvkh6fz4uegf3r84cj72zh7l606rt9x39zqvv8vxhku9luqss4zxy What's the file format? Is it human-readable and editable (which would be a workaround for ordering bookmarks).