Beagle: Git, URIs and all the dirty words

Beagle: Git, URIs and all the dirty words(replicated.wiki)

17 points by gritzko 2 days ago | 6 comments

PufPufPuf 53 minutes ago |

That seems unnecessarily cryptic -- the whole HTTP analogy doesn't really work well, or the article doesn't do a good job of explaining it. I know, I come from a place of knowing git and beginners are often confused by it... but surely "checkout a branch, make a commit" has a clearer mental model than "post ?branch!", whatever that is supposed to mean.

Contortion 36 minutes ago | |

Agreed. I think the code examples in the article could do with showing before and after states of the branch or repo and maybe compare with standard git commands.

Even then I don't think the abstraction to HTTP verbs is necessarily a useful one as web requests and version control are two different mental models.

gritzko 30 minutes ago | | |

Think of GitHub URIs. That is exactly version control mapped onto HTTP address space. So, nothing really special here.

But before/after state is indeed a thing to add.

OJFord 11 minutes ago |

"yo dawg, I heard you like confusing SVC CLIs" vibes

quantummagic 59 minutes ago |

I love the idea of building a new Git UI on top of Git primitives[1], but the REST inspiration leaves me feeling underwhelmed; there has to be a more human-friendly model.

[1] https://replicated.wiki/wiki/Home.html

gritzko 24 minutes ago | |

The most human-friendly thing is probably natural language. If so, it is LLMs who should have an intuition about the REST interface and its URI syntax. I personally would prefer to glance at it, but not to type it repeatedly. Especially, hashes.

So, the actual question is how to make this machinery un-screw-up-able. (Author)