htmx VS phoenix_live_view

https://pkg.go.dev/html/template on the backend and https://htmx.org/ on the frontend is the productivity dream.

https://htmx.org/ Says otherwise, so does https://blog.appsignal.com/2022/07/06/get-started-with-hotwi...

HTMX works well with any language, any backend and goes a long way. Unpoly too.

htmx for requests.

Of course it depends on your use case. But consider https://htmx.org/ together with go templates.

"HTML over the wire" generally refers to tech like [0] Liveview, [1] Hotwire, [2] LiveView, [3] Blazor, etc. They aren't about about ditching JS and more about not writing your HTML in JS (and yes, SSR).

[0] https://github.com/phoenixframework/phoenix_live_view

* https://github.com/phoenixframework/phoenix_live_view

Some of the 1.7 stuff has an alert banner that pops up when the connection is broken. I think that could really help.

However I haven't put that in our app as I have seen other issues of flakey connection reconnect issues, and I would hate to make any of those more visible with a flashing notice.

- https://github.com/phoenixframework/phoenix_live_view/issues...

HEEx template language was created, an extension to EEx

Also to your point, the latest LiveView release moved some helper utilities around and you need to add "import Phoenix.Component" in places. I could be wrong but I think the latest live code gen still isn't setting up correct imports. More info here: https://github.com/phoenixframework/phoenix_live_view/blob/master/CHANGELOG.md

If you need any kind of interactivity on the frontend, but are more comfortable with the backend, I would suggest looking at Phoenix LiveView [0] or a similar server-rendered HTML technology for your language of your choice [1].

In short, these solutions take JavaScript out of the mix entirely and basically let you deal with a single logical "app", rather than a separate frontend & backend.

[0] https://github.com/phoenixframework/phoenix_live_view

It uses JS though, as it is required to open a WS connection and change content without refreshing the page, but that looks like it is abstracted from the user. https://github.com/phoenixframework/phoenix_live_view/tree/master/priv/static

> I'm not up to date with the less popular web frameworks. Which frameworks do that?

One of them is https://github.com/phoenixframework/phoenix_live_view which is a component of Phoenix / Elixir.

It will render your initial page over HTTP but then when you transition pages or perform actions using various functions it provides you it will send a diff of what's changed over WebSockets. These actions could be limited to only the 1 user using the site, such as clicking different links in a nav bar to transition between page A and B.

The alternative to this is doing what other frameworks like Rails has done with Hotwire Turbo where they make these types of transitions of actions over HTTP. Turbolinks started to do this back in 2015 or whenever it came out and now more recently with Hotwire Turbo there's ways to only update a tiny area of the page (again over HTTP) but it also optionally supports using WebSockets for when you want to broadcast things to all connected clients, such as updating a counter somewhere or maybe showing a new reply on a blog post, etc..

Laravel has Live Wire and there's also HTMX which is back-end agnostic which all use HTTP for a bulk of their behaviors to send server rendered HTML over the wire.

I think Phoenix even has a templating framework for the front-end, called LiveViewer (https://github.com/phoenixframework/phoenix_live_view). And i believe it uses the built-in websockets to communicate changes on front-end to the server.

The context: I'm building a cryptocurrency exchange application. I don't have the business chops to run an actual exchange, so this is just for fun. The application is built in Elixir, using the Commanded framework for CQRS/ES goodness, and Phoenix LiveView because it's the hot new thing that I wanted to learn.