Is your disinterest in LiveView because you'd prefer the more common SPA/API separation, or some other reason? I'm curious because as a mostly backend engineer I view LiveView as sort of a killer tool for the sorts of apps or tools I'm likely to build.
Not the parent, but since the liveview state is on the server side it means that one server can't support a large number of concurrent sessions, for some value of large.
I just strongly dislike the layout engine ;) Also yeah deployment with active socket connections is not always ideal.
Not writing api routes for the frontend (when you don't also have a mobile app etc) is nice though, and pairing it with PubSub for UI updates is a cool trick.
