In contrast to the classical OS model, our system blurs or
eliminates many of the typical boundaries between software, hardware, kernels,
and drivers. Most uniquely, there is no single piece of software or hardware in
our architecture which corresponds to the kernel in a classical OS. The operat-
ing system is instead an emergent entity arising out of the collective behavior
of a series of distinct hardware modules connected via message passing, which
together provide all of the services normally provided by a kernel and drivers.
Each hardware device includes state machines which implement low-level re-
source management and security for that particular device, and provides an API
via message passing directly to userspace. Applications software may either access
this API directly (as in an exokernel [2]) or through server software providing
additional abstractions (as in a microkernel).

The editing trace has 260 000 edits, and the final document size is about 100 000 characters.

As I said above, automerge takes a little under 5 minutes to process this trace. Thats just shy of 900 edits per second, which is probably fine. But by the time it's done, automerge is using 880 MB of RAM. Whoa! That's 10kb of ram per key press. At peak, automerge was using 2.6 GB of RAM