--- title: "Live Preview for Large LuaTeX Documents" date: "2026-07-19" canonical: "https://raytally.com/en/ideas/2026-07-19-real-time-luatex-recompiling-large-documents-in-1ms-pdf/" generator: "RayTally · dev-prompt-v4" signal: query: "Real-Time LuaTeX: Recompiling Large Documents in 1ms [pdf]" observed_at: "2026-07-19T01:33:02.331Z" sources: - url: "https://news.ycombinator.com/item?id=48962944" boundary: "Published at 2026-07-18T00:00:00.000Z. Observed at 2026-07-19T01:33:02.331Z." - url: "https://www.texlode.com/" boundary: "No publication timestamp is present in the source record." - url: "https://docs.overleaf.com/navigating-in-the-editor/working-with-the-pdf-viewer/moving-between-the-editor-and-pdf" boundary: "No publication timestamp is present in the source record." - url: "https://github.com/let-def/texpresso" boundary: "No publication timestamp is present in the source record." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-19-real-time-luatex-recompiling-large-documents-in-1ms-pdf/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Live Preview for Large LuaTeX Documents Change one line in a large LuaTeX document and see the affected PDF pages update in milliseconds, with a link back to the source that caused each refresh. ## Product concept When authors of long technical documents change a reference, formula, or chapter, the editor recomputes only the affected portions and replaces the updated PDF pages in place. Each partial refresh can trace back to the source line that triggered it, preserving sophisticated typesetting while providing feedback close to that of a plain-text editor. Authors can expand the dependency relationships to see why a one-line edit changed particular pages. ## Why now (backed by facts) A preprint about recompiling large LuaTeX documents in “1ms” appeared on Hacker News on July 18. In a snapshot at 1:33 UTC on July 19, it had 26 points, 4 comments, and rank 19, suggesting the problem drew one round of community attention during this short observation window, but not supporting an inference about long-term demand. ## Direction (model inference, not independently verified) Target user: LaTeX authors maintaining theses, technical books, specifications, or large research reports. They open it after adjusting formulas, citations, footnotes, figures, tables, or chapter structure to immediately see which pages moved and why the change propagated. Minimal entry point: Start with a local VS Code extension for a defined, verifiable set of LuaLaTeX document structures and common packages. A persistent compilation process records dependencies among source files, auxiliary files, and output pages, then replaces the affected pages after each change; integrate source-to-PDF navigation directly through SyncTeX. The strongest case against: The hard part is not refreshing the PDF but guaranteeing that the incremental result is correct. Floats, page numbers, tables of contents, cross-references, footnotes, auxiliary files, and custom macros can cause a one-line change to propagate across paragraphs or even chapters. If the dependency graph misses a single edge, authors get a fast preview with stale content; relying frequently on full compilation as a fallback also weakens the speed advantage. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Build an open-source editor integration layer and compatibility-test repository, using public paper, thesis, and book templates for reproducible comparisons with full compilation. Collect failure cases through Hacker News, TeX Stack Exchange, and LaTeX communities, then turn the findings into a searchable package-compatibility list. ## Competitors & gaps (model inference) - tex lode: It already claims paragraph-level incremental compilation with LuaTeX and uses live preview in book publishing workflows. The opening is to support existing LaTeX projects and code editors, emphasizing affected-page replacement, source backtracking, and expandable dependency explanations. - TeXpresso: It can already re-render changed portions of a document and synchronize the editor and preview in both directions, but it remains in early development and uses a customized XeTeX. The opening is LuaTeX project compatibility, in-place PDF page updates, and an explicit dependency graph. - Overleaf: It already offers SyncTeX-based two-way navigation between source and PDF. That post-compilation navigation could be extended with affected-page markers and causal explanations for every incremental update. ## How it makes money (model inference) Offer an annual individual subscription that includes the local editor plugin and ongoing updates; sell seat-based licenses to universities, labs, and publishers. ## Source context Theme: Millisecond live recompilation for large LuaTeX documents Trigger Hacker News post (original English): Real-Time LuaTeX: Recompiling Large Documents in 1ms [pdf] Heat at capture: ~26 points, 4 comments (point-in-time values) Points and comments are a historical snapshot from the moment of capture and drift over time. They only explain “why now”; do not present them as precise market numbers. ## Sources - Real-Time LuaTeX: Recompiling Large Documents in 1ms [pdf] (https://news.ycombinator.com/item?id=48962944) - tex lode — Real-time LaTeX book editing (https://www.texlode.com/) - Moving between the editor and PDF (https://docs.overleaf.com/navigating-in-the-editor/working-with-the-pdf-viewer/moving-between-the-editor-and-pdf) - TeXpresso: live rendering and error reporting for LaTeX (https://github.com/let-def/texpresso) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.