Hacker News Reader

Comment by darnfish | Hacker News Reader

Reminds me a little of https://github.com/calderajs/caldera-react

Cool. LiveViewJS (and Phoenix LiveView) renders the initial HTML over HTTP but then connect to the server via a persistent web socket connection. Client events (clicks, form updates, blur/focus events, key events, etc) are then sent over the socket which kicks off a server-side state updates and rendering with only the diffs sent back over the web socket. These diffs are then merged with the existing dom. (Maybe TMI here but wanted to be clear this isn't just server-side rendering over HTTP.)

It sounds like you're describing the same thing: https://github.com/calderajs/caldera-react

> Think of it as the Node.js analog to Phoenix LiveView — all of the application logic (including rendering) runs on the server, and DOM updates are sent to the client in real-time.

Gotcha. I read the README and it wasn't clear to me that this is how Caldera works. Sorry about that.

I'll add that the API for implementing components in LiveViewJS follows the Phoenix API (mount => handleParams => handleEvent => render) rather than the React API.

I made (no longer working on it); https://github.com/justinmcp/taper, which is essentially, react + "redux on server" - so still rendering on client, but logic in server.

It's definitely an interesting space to explore, I will take a look @ caldera, seems like an interesting project!

Reply on news.ycombinator.com