[hellofunk]

I can't tell what your description of LiveView is suggesting, I will need to read about it, sounds interesting. Is it like a codebase that is implicitly split on a back-end and a browser, without the need to write JavaScript?

[Existenceblinks]

Phoenix LiveView is the Google Stadia of web app. Browser is just like a console for sending commands over an established connection (stateful) to server. It's pushing computation and state management to servers, and eliminating a lot of steps e.g. encoding huge internal data structure to json, api endpoints design, huge javascript downloading and parsing, re-rending that data with template on client side. If you use a compile-to-js language on frontend, the extra step is to decode json into internal types as well.

LiveView is the haven for apps that are focusing on B2B and internal tools in organizations. Because it doesn't have to support offline usage, and cost effective since you don't have to have a frontend team.

[cuddlecake]

Phoenix LiveView is basically server side rendering in real time.

The user's actions are sent to the Backend via WebSocket, and the Backend rerenders (parts of) the view and sends them to the user.

[jacobush]

But ... why? Sends it back as ... HTML?

[lawik]

Not really, the frontend caches the static parts of the template and the backend only needs to resend the dynamic, changing, parts.

So "Welcome to $mysite, $username." would initially send the full rendering but if the data changes it would only send "Hacker News,lawik" over the wire. Somewhat simplified.

This covers it quite well: https://www.youtube.com/watch?v=8xJzHq8ru0M

[nyadesu]

pretty much like .NET Blazor and SignalR