Herb to ReActionView
summary
Herb supplies an HTML-aware ERB parser (implemented in C), a language server that gives real-time editor diagnostics, a formatter, and a linter with 50+ lint rules and a Tailwind plugin for class ordering. The Herb engine renders ERB with debug outlines, injects file and position attributes for jump-to-source, and shows exact parse errors in the browser. ReactionView wires Herb into Rails via a generator so ERB files use the engine out of the box and enables experiments like reactive templates and per-part render timing.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:20Better Ruby view tooling
- 6:07Herb and ReactionView
- 9:18Herb’s HTML parser
- 10:42Herb language server
- 12:28HerbLinter
- 13:54HerbFormatter
- 16:05Herb engine
- 17:31Debugging views
- 20:19ReactionView vision
- 21:02Setting up ReactionView
- 22:29ActionView optimizations
- 22:51Reactive templates
- 23:35External components
- 24:36Call for partners
- 24:56Herb’s ecosystem impact
- 26:42Learning with Herb
- 28:05Ruby view layer future
- 28:47Closing
related talks
37mKeynote: Herb to ReActionView: A New Foundation for the View Layer
32mHTML-Aware ERB: The Path to Reactive Rendering
32mIntroducing ReActionView
34mThe Modern View Layer Rails Deserves: A Vision for 2025 and Beyond
31mThe Anatomy of an ERB Rendering Engine
42mRender It! A Deep Dive into ActionView and Template Engines
38mRethinking the View Layer with Components
44m"The View Is Clear from Here"