unsplit VS liveviews

If I recall correctly, if some node desyncs, it's hard to get it started again. You have to manually transfer the entire database from another node which can obviously take a long time if you have a large database. It doesn't really handle netsplits by itself (there's https://github.com/uwiger/unsplit) so you have to be prepared to do this yourself.

If you want to try the liveview approach but not ready to work with Elixir / Erlang / Beam runtime, you can use liveview in 17 popular languages (Java / C# / Javascript / Typescript / PHP / Python, e.t.c.).

https://github.com/liveviews/liveviews

Below are introduction directly quoted from this list:

> This is a list of libraries for creating web applications that handle user interaction with the DOM on the server. These libraries take a different approach from older server-driven browser UIs that simulated a desktop GUI toolkit. They do not lock the developer into working with predefined components; most operate at the level of HTML (DOM) rather than GUI widgets.

> The list strives to be complete rather than awesome. You may see libraries that are not maintained or ready for production.

This approach allows you to handle business logics on the server, and update the screen in browser from the server as well.

[1] https://github.com/liveviews/liveviews

That's a conflation. I'm certain for at least some, the choice is more about using a single language than avoiding JS. I'm sure there are people using htmx who use a JS backend. There are at least 5 LiveView clones for JS for instance: https://github.com/liveviews/liveviews#javascripttypescript

Nuxt, Next, SvelteKit, Phoenix(Elixr), Blazor, and various liveview-likes are popular full stack frameworks. So, although many devs are becoming specialized, there certainly still are full stack developers with demand enough to strongly support several frameworks.

The list is seeking a maintainer. https://github.com/liveviews/liveviews/issues/23

> "different" platform with it's own unique patterns and quirks

Everything OP listed was a criticism directed at LiveView, the 'Live App' functionality, not Phoenix, the web framework. Live Apps are not exclusive to Phoenix either, as there are now imitators for every other web framework now, which at least speaks to its broader appeal amongst developers. So the criticism could be leveled towards the far less mature 'Live App' libraries on PHP/Python/JS/C# and so on and on:

https://github.com/liveviews/liveviews

However there are two ways you can do this server side: 1. Use a tool similar to live view: https://github.com/dbohdan/liveviews