How we got to LiveView

Re:How we got to LiveView by akoutmos on Wednesday September 22, 2021 @04:48PM (#28621583)

For a lot of the LiveView applications that I write (which is actually quite a few these days), I will usually lean on something like AlpineJS for frontend specific interactions, and my LiveView state is for things that require backend state.

For example, if I have a flag to show/hide a modal to confirm a resource delete, the show/hide flag would live in AlpineJS, while the resource I was deleting would live in the state of my LiveView.

This way, there are no round trips to the server over websocket to toggle the modal. Hopefully that example makes sense :).

[ Parent | on HN ]

Re:How we got to LiveView by cs44 on Wednesday September 22, 2021 @06:08PM (#28622623)

I'm surprised to see so few mentions of AlpineJS. Personally, PETAL has become my de facto stack.

[ Parent | on HN ]

Re:How we got to LiveView by AlchemistCamp on Thursday September 23, 2021 @12:46PM (#28631691)

The main thing that's kept me from using Alpine in my serious projects is that it doesn't work with a strict CSP.

[ Parent | on HN ]

Re:How we got to LiveView by brainbag on Thursday September 23, 2021 @12:02AM (#28625096)

What is PETAL?

[ Parent | on HN ]

Re:How we got to LiveView by sarchertech on Thursday September 23, 2021 @12:15AM (#28625159)

Phoenix, Elixir, Tailwind, Alpine, and LiveView.

https://changelog.com/posts/petal-the-end-to-end-web-stack

[ Parent | on HN ]

Re:How we got to LiveView by iruoy on Thursday September 23, 2021 @08:01AM (#28627983)

The PHP equivalent would be the TALL stack (Tailwind, AlpineJS, Laravel and Livewire). Although Livewire just communicates over AJAX. The original Websockets version didn't make it.

I just found out that Livewire was inspired by LiveView.

[ Parent | on HN ]