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/?)
Julia Evans /
npub1ym…nlm9y
2024-03-12 13:20:19
Author Public Key
npub1ym9ddu2qh7rda8pxklq4gxw2kxhtm4cgvdvdy64z6agwy88nhuhqcnlm9yPublished at
2024-03-12 13:20:19Event JSON
{
"id": "54515306c6c9e7379ef7355a731ad8a88b2a5349b915790732e6f9a1969f5d43",
"pubkey": "26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"created_at": 1710249619,
"kind": 1,
"tags": [
[
"proxy",
"https://social.jvns.ca/users/b0rk/statuses/112082919095290106",
"activitypub"
]
],
"content": "this morning I'm thinking about how git's history of being built as a series of shell scripts has affected its user experience\n\nmy sense is\n\n1) a lot of git was originally built as shell scripts\n2) the user experience you can provide in a shell script is extremely limited\n3) a lot of that now can't change for backwards compatibility reasons\n\ndoes anyone have examples of this? will talk about how I think this affects merge conflicts in the next post\n\n(1/?)",
"sig": "cc087c3bacf06703fec8dd1eb0ae8791231e22829e46bc50f40121dd821de93bbcb06e8475b1ff6fbccb716611fb098dbafedd0f02873439961bce82e4f080c9"
}