Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @PuercoPop@mastodon.social
dave@dthompson@toot.cat (2026-09-25 04:47:57)
@PuercoPop all that stuff would be very possible with the right primitives and I think ocapn plays a role in that. on top of ocapn you could do crdt-based collaborative editing sessions. collaborative structural editing is my long term goal.
---Reply---
PuercoPop@PuercoPop@mastodon.social (2026-09-25 05:45:14)
@dthompson Yeah, I read the CRDTs Byzantine Fault Tolerant Paper mentioned on the Spritely blog. There are already some nice prototypes of guile based editors like zem https://github.com/Jimx-/zem/. Although it might be better to think of the editor components in terms of actors. I've grown increasingly disillusioned with the shortcomings of GNU Emacs. Functions like sit-for are a hack that have lived for two long.
Reply
---Replies---
PuercoPop@PuercoPop@mastodon.social (2026-09-25 05:46:42)
@dthompson But it is tricky to determine the right level of granularity. e.j. one actor per buffer, but with multiple buffers on the same file there would need to be coordination (locks?) across actors to ensure only one is saving a buffer a given file at the same time