the purpose (from the paper):<p>> texlode, the browser-based book editor built
on this architecture, is scheduled for public release in
October 2026. It provides collaborative editing via
conflict-free replicated data types (CRDTs), manu-
script import from Word, proceedings management,
cover design tools, and print-ready PDF output iden-
tical to standard LuaLATEX. The accompanying con-
ference talk demonstrates the editor in action. For
details: texlode.com.<p>and also:<p>> (section) 6 Comparison to Typst
Typst taking 300ms to do 300 pages cannot be seen as 4FPS - you don't treat the sum of 300 pages as single frame, LOL. And laying out a single paragraph is not 1ms for a whole document either. The paper is otherwise pretty good, but these rhetorics are probably not necessary, IMO.
Personally, I am enjoying using Typst.
> Benchmarks show that per-paragraph recompilation achieves O(1) latency, constant regardless of document size, whereas Typst’s [3] incremental compilation scales linearly (O(n)).<p>> The tradeoff is temporary inconsistency: pages the user is not viewing may lag until a background
compile converges, [...]<p>There doesn't seem to be any reason functionality like this couldn't also be added to Typst though. In general the authors of this paper seem dismissive of typst, but Typst also fixes so many other things about LaTeX, like the awful syntax. Not sure why they act like that.
No mention of TikZ. Realtime TikZ would be really useful to me. I will wait and see what their <a href="https://texlode.com" rel="nofollow">https://texlode.com</a> service is like for that.