Transactional memory for operational transformation in Leisure
It's been a very long time since my last post but we haven't been idle. We've been working on Leisure, which grew out of Lazp. Leisure has become a collaborative, dynamic, polyglot, computing environment, but more about that in future posts. If you're curious about Leisure, you can find the repository here , although we haven't formally announced it, yet. It's functional but buggy. For now, here's a short note about how Leisure manages collaborative data manipulation. Leisure's collaborative documents contain a combination of content, code, and data, all represented by org-format markup in plain text. Data in Leisure documents resides in markup-delimited regions of text, such as org-mode source blocks containing yaml data and code in a Leisure document can change that data. This means that, beyond just normal collaboration, Leisure requires an exclusion mechanism so that data can stay consistent when several users access and change it. Curre...