Liveview / livewire

I've used Livewire on a couple of projects. I think it works pretty good for admin areas, once you get used to thinking that way. From what I've seen Pheonix Liveview is probably more optimized than Laravel LiveWire.

My take is that for a website that just needs some simple interactions Livewire can work pretty well. But you miss out on some of the more advanced UX experiences. And, as users are spending more on more time in apps, I feel they're starting to expect that app-like experience more and more from their websites. So many large websites have jumped on board the Javascript train for frontends I've come to the conclusion that trying to keep everything in PHP is great for simple sites, but at a certain point you just can't provide the experience users and clients are often looking for.

I had started to work on a Livewire-like implementation for Bonfire before I decided that my personal project(s) needed a better UI. I use React at the day job, but my current personal project is in Svelte.  Still exploring that.

To sum up (too late, I know ) Llivewire-like code definitely has a place, but I think we shouldn't be too beholden to staying within PHP and should definitely take the time to learn other front-end tools. Then the job is deciding which is the best resource to use when.

Great points, it's funny because I'm coming from the tail end of the SPA honeymoon period, after working with Angular, react, svelte, and eventually diving into Elm. (My personal opinion if I had to choose, Elm would come out top but it has much too low of an adoption point to invest time into.) The trouble is, I have no other conclusion to draw except the SPA way of life, is utterly maddening, especially when you take into account the webpack / vite builds, SSR, and state management, so liveview looks very promising.

As elixir is made for this I'd imagine it would have better performance. But I mean, there is that issue of injecting html directly into the dom, and having another AST to do the dom parsing, which is a non trivial topic. I'm not sure how Caleb Porzio, is doing the implementation but I did hear he was using either using websockets, or just vanilla ajax with debouncing.

It is definitely an interesting one. I'm starting to encounter issues with sprinkling vue components on the frontend but then passing that post data back to the backend.

Practical guide to IgnitedCMS - Book coming soon, www.ignitedcms.com