[bcardarella]

I never used ASP.net so I cannot offer a comparison about what is "better" but your assumption is correct that diffs are through a WS and merged client-side. What this has resulted in is actual order of magnitude of implementation time reduction over the crazier SPA complexity available today. Less time to build, less cost to the company, less bugs in the long run, and a single place to manage and reason about state. It's a win.

[bornfreddy]

But isn't there a delay in UI responses because of latency then?

[cmoski]

You keep frontend UI changes that don't affect state in the frontend. If you don't need the server then you don't waste your user's time with trips to the server. If you need server, you can do things on the frontend at the same time you send the request, e.g. hide something, add/remove a class.

[cess11]

Sure, it's not for a smooth user experience over 2G connection, if that's your audience you'd use ordinary template rendering with Phoenix, or use it for a JSON API and build a JS client that talks to it.

[bornfreddy]

I can see the next big thing coming: no latency! Render in client! :)

[cess11]

Seems maybe messy to have templating in the client but I'd take a look if someone has done it.

[swarm_commerce]

https://github.com/dwyl/phoenix-liveview-todo-list-tutorial