I found the timing super interesting because just one day after the Logseq 2.0 announcement, another tool announces a rewrite. Checking this now.