To the new Livewire developer, the experience is somewhat magical. It feels as if when the page loads, your Livewire component is living on a server listening for updates from the browser and responding to them in real-time.
This is not far from how other, similar tools like Phoenix LiveView work.
However much Livewire feels similar, it has quite different inner-workings that have their own sets of pros, cons, and security implications.
Livewire components feel “stateFULL”, however, they are completely “stateLESS”. There is no long-running Livewire instance on the server waiting for browser interactions. Each interaction is an entirely new and fresh request/response.
To more fully grasp this mental model, let’s use the foll