E.g a personal note-taking app where the user will never have any collaborators, but where they expect the app to work fully offline on multiple devices and reliably sync up when they come online.
Automerge-Repo: A "batteries-included" toolkit for local-first applications
31–40 of 45 posts
Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#32Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#33Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#34Earlier quoted context omitted.
Ouch Peter. Massive offense taken. > In our research, we've found that editing is usually serial or asynchronous. Medium-to-large-size company with a town hall = many people editing a document at the same time. Workshop at a company or a university with a modest size classroom = many people editing a document at the same time. I can't tell you how many times our web-based collaborative code editors would fall over du…
Please accept my unreserved apologies, Heather! No offense is intended. I can speak for everyone working on Automerge when I say that we've very much appreciated Matthew's work and have indeed spent quite a lot of time studying and responding to it. We spoke about it in person last week, in fact. As for the use-cases, I do not mean to exclude live collaboration from consideration, just to note that it hasn't been our…
I’d love to hear more about this. Do you elaborate anywhere?
Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#35Congrats! Many moons ago the lack of undo/redo was the main blocker. Has this been added?
For applications with more document-structured data, you can now produce inverse patches using Automerge.diff to go between any two points. To implement a reasonable undo in this environment you can record whatever document heads you consider useful undo points and then patch between them.
To perhaps expand on why the problem remains unsolved slightly further, there was a robust discussion about what the expected behaviour of "undo" out to be in even simple cases at the conference.
Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#36Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#37This is exciting in several ways including the fact that Martin Kleppmann is involved with the project. Filed at the top of my reading list if nothing else to see an undoubtedly good example of a complex Rust project.
Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#38So is it like https://en.wikipedia.org/wiki/Google_Wave - but with limited scope and with new algos and finally usable?
Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#39Re: Automerge-Repo: A "batteries-included" toolkit for local-first applications
#40Would Automerge be a good choice for a non-realtime single-user app that just needs to have reliable offline support? E.g a personal note-taking app where the user will never have any collaborators, but where they expect the app to work fully offline on multiple devices and reliably sync up when they come online.