3 ms·

I always believed that side-by-side diff view is a transclusion interface. Also, permalinks can work on top of git quite nicely https://replicated.live/blog/li

by gritzko 28d ago

I always believed that side-by-side diff view is a transclusion interface. Also, permalinks can work on top of git quite nicely https://replicated.live/blog/link https://replicated.live/blog/link If git's pack index gets refactored slightly, it can do anything from trigram-indexed search to metadata indexing to hyperlinking both ways across repos. That is actually useful, I use it: https://replicated.live/blog/wiki https://replicated.live/blog/wiki CRDT merges are a very incremental and useful upgrade for git https://replicated.live/blog/meta https://replicated.live/blog/meta Xanadu-like functionality is perfectly within reach. We don't get what we want or what we need. Instead, we move erratically in very small, easy, local steps.

TheOtherHobbes 28d ago
Word's Track Changes is very transclusiony. It's not a bad UI metaphor for limited applications, but it makes no sense at all for a global document store. Humans like boundaries. Even ignoring the copyright issues, we like our cultural artefacts to have edges and a limited number of interaction modes - basically read/consume, write/publish, mention/reference, and converse/comment. Massively cross-linked semantic soup isn't one of those modes. Text artefacts need to be stable - it's a core requirement - or at least mutable in very, limited and controlled ways. Music has sampling and LLMs have style transfer, but text with mutable semantics is a weird animal and not really how we do things.
- gritzko 28d ago
  I am not in the contract negotiation business, but I had that experience. Speaking of git-with-permalinks, it implies that you have some repos locally that may want to link to each other. Like your code in 4 different repos, one repo with tickets, one wiki, and some other stuff. It is especially helpful if agents leave cross-references to have some trail for the decisions. Agents, generally speaking, have no memory, so each time they recover the context from scratch. When I read what they coded, I essentially do the same. So, permalinks and transclusion are practically useful. T.H.Nelson picked up that idea in the movie industry, I hear. They furiously edit their scripts and contracts, I suppose.

by gritzko 28d ago

TheOtherHobbes 28d ago

Word's Track Changes is very transclusiony. It's not a bad UI metaphor for limited applications, but it makes no sense at all for a global document store. Humans like boundaries. Even ignoring the copyright issues, we like our cultural artefacts to have edges and a limited number of interaction modes - basically read/consume, write/publish, mention/reference, and converse/comment. Massively cross-linked semantic soup isn't one of those modes. Text artefacts need to be stable - it's a core requirement - or at least mutable in very, limited and controlled ways. Music has sampling and LLMs have style transfer, but text with mutable semantics is a weird animal and not really how we do things.

gritzko 28d ago
I am not in the contract negotiation business, but I had that experience. Speaking of git-with-permalinks, it implies that you have some repos locally that may want to link to each other. Like your code in 4 different repos, one repo with tickets, one wiki, and some other stuff. It is especially helpful if agents leave cross-references to have some trail for the decisions. Agents, generally speaking, have no memory, so each time they recover the context from scratch. When I read what they coded, I essentially do the same. So, permalinks and transclusion are practically useful. T.H.Nelson picked up that idea in the movie industry, I hear. They furiously edit their scripts and contracts, I suppose.