> 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.
and also:
> (section) 6 Comparison to Typst
I know its a lot of work but I think we all could desperately use an interactive LaTeX notebook instead of limiting it to only the PDF backend and this work helps a lot with achieving that endeavour. Though it'll be limited to LuaTeX, it'll still be quite something.
The experience was just like using Word, but with LaTeX.
Unfortunately not the kind of stuff the vi and emacs folks care about.
Although LyX comes close.
> The tradeoff is temporary inconsistency: pages the user is not viewing may lag until a background compile converges, [...]
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.
If I have to guess it's because the temporal inconsistency tradeoff can actually affect the current page too, since it might depend on the previous pages for layout, references, etc etc.
Typst on the other hand aims to have no inconsistencies due to incremental compilation.
They seem to launch paid competitor.