I assume you’re asking about the second part of that quote - “solving the DOM synchronization problem that LiveView can’t address.”
The fundamental issue is that the DOM is inherently stateful and LiveView’s architecture creates an unavoidable state consistency problem between DOM and server that requires ongoing reconciliation.
Here’s what happens in LiveView:
- User types “A” → DOM state becomes “A” (immediate)
- Event sent to server → server state becomes “A” (delayed)
- Server sends update back → client reconciles DOM with server state (delayed)
This creates all the fundamental distributed systems challenges: consistency problems, latency, ordering issues, partition tolerance, and failure modes (server restarts, connection drops, deployments, etc.). The DOM maintains its own internal state (what the user sees and interacts with), while the server maintains application state. Fast typing, network issues, or server processing delays create windows where these stateful systems are inconsistent, and the failure modes described above can result in complete state loss. During steps 2-3, you have two sources of truth that can diverge. LiveView’s client-side hooks are constantly working to reconcile these differences across the network boundary.
In Hologram:
- User types “A” → DOM state becomes “A” (immediate)
- Hologram updates component state → component state becomes “A” (immediate)
- DOM and component state remain synchronized (always)
There’s never a consistency gap because the DOM’s inherent statefulness is managed within the same execution context as the component state - one source of truth that gets updated atomically.
The key difference: LiveView must continuously resolve state inconsistencies between the inherently stateful DOM and server, while Hologram prevents state inconsistencies from occurring in the first place.
While LiveView’s hooks provide some mitigation, they’re fundamentally limited by the distributed architecture - solving a problem that Hologram’s architecture simply doesn’t have. You can’t have DOM/server synchronization issues when the DOM’s stateful nature and application state are managed in the same execution context.
That’s what I meant by “can’t address” - LiveView can’t eliminate the fundamental architectural challenge of coordinating two separate stateful systems, only manage it.
