The Modern View Layer Rails Deserves: A Vision for 2025 and Beyond
summary
A concrete stack appears: Herb parser in C (built on Prism) produces a unified HTML+ERB AST, plus a formatter, linter, rewriter and a VS Code extension and language server that already surfaces diagnostics for missing ends and broken tags. Early prototypes demonstrate editor autofix, CLI linting and pretty printing, and a proof‑of‑concept ReActionView reactive ERB engine that opts in via new file types to enable HTML‑aware compilation and LiveView‑style incremental updates.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05Action View history
- 4:41Rails view tooling limits
- 11:04Introducing Herb
- 14:12Herb’s parser
- 14:32Herb’s formatter
- 15:33Herb’s linter
- 18:00Herb’s tools
- 19:44Herb’s language server
- 22:17New ERB rendering engine
- 24:46Reactive templates
- 26:31Herb’s impact levels
- 32:34Next steps
- 33:17Closing
related talks
32mIntroducing ReActionView
30mHerb to ReActionView
38mRethinking the View Layer with Components
32mHTML-Aware ERB: The Path to Reactive Rendering
34mCurly — Rethinking the View Layer
35mFrontendless Rails frontend
44m"The View Is Clear from Here"
32mModern JavaScript, without giving up on Rails Jonathan Johnson