@manlycoffee @pbnotes Interesting! Wonder how an immutable ledger will scale to thousands of notes and tens of thousands of edits. Scaling is often the bottleneck of ledger-based storage, right? Huge fan of block-based outliners though!
Thanks!
I tried this with a million events, more than 16 thousand pages, and 400 thousand blocks in the graph, written over a span of 22 years, which comes to around 2 pages per day, 50 blocks, with 12 deletions and 12 re-creations, and half the blocks get edited.
It's hoping on the fact that users persist their notes on an NVMe drive, and have at least 2 GiB of RAM available (that they are using in a ridiculously lightweight window manager on Linux, but 8GiB otherwise). Loads up in about 23s seconds at startup. Which is still unacceptable, but I will work on a persisted fold/projection of the events that pickup where the app last left off in the last projection.
I'm not saying concerns around an event-oriented system is wrong.
But it is a tradeoff that I took on, because conflicting writes on a page was a problem for me, which I admit is a minority of people who have a problem with it, considering Obsidian is fairly popular, compared to Logseq, and Obsidian's model is pure Markdown files.