Martin Kleppmann

Hi @skokenes, I've been doing some work on improving load times (#436) and with that new backend I see a 11x speedup in loading your document. It's still not as...

The Rust/Wasm implementation of Automerge is now providing good performance and we are in the process of moving the JS API to being a wrapper around the Wasm module, so...

I have put an initial attempt on the [immutable-api](https://github.com/automerge/automerge/tree/immutable-api) branch. No tests yet, so the code may well be broken. If you get the document object through `Automerge.initImmutable()` instead of...

I merged in the read-only Immutable.js-compatible API in #62, but will leave this issue open until we have support for the Immutable.js mutation methods as well.

Hi @alizain, I agree that it would be great to have several implementations in different languages that can produce/consume the same JSON format and thus synchronise their changes. However, I...

@sdedalus We're hoping to merge the performance branch into main and make a 1.0 preview release in the next week or two. That will include the last remaining breaking changes,...

I think it's actually a desirable feature to keep as much history as possible, since it can be a useful feature in its own right (a sort of poor man's...

We are getting a lot better at storing history efficiently, as discussed in #253, so the need for clearing history entirely is less pressing. Nevertheless, as I have said previously,...

Oh, I should also mention — one simple way of clearing history is to create a new document with a copy of an existing document's state, e.g. like this: ```js...

Hi @FelixSelter, thanks for writing this up. I think the code example is not quite correct though. If I read it correctly, you're taking a message from `Automerge.generateSyncMessage()` and broadcasting...