Comment by aeonfox
10 hours ago
I assume Django LiveView is directly inspired by Phoenix LiveView. It's essentially diffing template expansion on the backend and sending patches to the frontend via websockets where JS then applies the patches. Clicks and other interactions are also transmitted to the backend where state for the socket is updated and the template is reevaluated, hence completing the loop.
The concept is correct, but it's a bit simpler Its architecture is explained in the documentation, that's why it's so fast!
I looked(admittedly briefly) and couldn't find the architecture explanation in the docs here: https://django-liveview.andros.dev/docs/
I apologize, I assumed the architecture would be understandable from the examples. I'll keep that in mind!