How we got to LiveView • Hacker News Board

Re: How we got to LiveView

#291

Post by redbar0n » Sat, Sep 25, 2021, 6:57 AM UTC

midrus wrote: post #256

besil wrote: post #180

Earlier quoted context omitted.

How Unpoly differ from Hotwire (Turbo+stimulus) or htmx+alpinejs? https://htmx.org/ https://alpinejs.dev/ https://turbo.hotwired.dev/ https://stimulus.hotwired.dev/

(My opinions) Compared to Hotwire: I think hotwire is the best option if you're using Rails. From what I know, hotwire needs a lot more of backend "collaboration" than Unpoly, so you will need backend "hotwire" implementations. You can see these things are being built for django, etc. Compared to Htmlx+ Alpine: Let me start with the disclaimer that I think Alpine.js is an aberration. Writing code inside html attribut…

I’d try Inertia.js compared to Unpoly. It seems a more modern alternative. It’s like HOTwire Turbo (aka. Turbolinks), but with JSON over the wire. But no API needed.

Re: How we got to LiveView

#292

Post by aabbcc1241 » Sun, Sep 26, 2021, 4:49 AM UTC

A bit side track, if you want to use the liveview feature but not ready to develop with dynamic type language (Phoenix LiveView is based on Elixir), and being more familiar with the node.js ecosystem, checkout ts-liveview (which is based on Typescript)

Re: How we got to LiveView

#293

Post by aabbcc1241 » Sun, Sep 26, 2021, 4:54 AM UTC

sgrytoyr wrote: post #35

chrismccord wrote: post #2

Creator of Phoenix here. I'm happy to answer any questions folks have about LiveView, Phoenix, or Elixir in general. We've had some big LiveView features land recently with uploads and HEEx so now's a great time to jump in!

Almost every time I see a discussion about LiveView there’s someone complaining about the issue of latency/lag, and how it makes LiveView unsuitable for real-world applications. From what I understand, the issue is that every event that happens on the client (say, a click) has to make a roundtrip to the server before the UI can be updated. If latency is high, this can make for a poor user experience, the argument goe…

A better balance would be to build the webapp in hybrid mode, some logic can be run by client-side javascript. Only the event handlers that rely on data from the server needed to be sent to the server.

In this pixel paint demo, the state and reaction of "changing the pen color" can happens locally: https://github.com/beenotung/live-paint/blob/dd3b370/server/...