The Pros and Cons of Laravel Livewire

[@alexandersix_]

With regards to Filament's table builder, we're currently working on optimizing as much of it as possible to help with performance. We've been shifting things over to Alpine for performance increases wherever possible, but there have been a few limitations of it for our specific use-case that we need to overcome in order to move tables entirely over to Alpine. We've been optimizing tables like mad in other ways though, and we're showing roughly a 2-3x performance increase in our testing at the moment for the next version of Filament! Those are benchmark numbers though, so I'm excited to see what the real-life performance gains are when v4 is released. 💛 It's wild how complex datatables get (in the TALL stack or with front-end libraries), especially as you start to explore the final 20% of edge cases, polish, and functionality. Amazing that something so simple can end up taking so much time to get right!

[@tariksadiku4723]

I feel like the problem with Livewire is that, unfortunately you are going to shoot yourself in the foot if you do not learn its ways (how to avoid re-renders and so on). If by proclaiming that is is simpler than frontend frameworks, we still need to learn it's sort of way of how it works, wouldn't that time be better spent in learning Vue (which is quite simple) to begin with? It feels like either way we go, we still need to learn on how it operates, and if it is the same amount of time, might as well spend that time on another part of the web which is super useful.

[@clayton.schneider]

This is a pretty interesting argument. I guess the big selling point of livewire is how it integrates with laravel a bit more then other Frontend frameworks. But with inertia does that even matter?

[@jonatasbaldan]

I think the docs of Livewire do a good job explaining the tecnics and techs that is used under the hood with good examples and follow ups.

[@abuhurairah7042]

I did exp build with react, vue, livewire, all frameworks have their ways once you're into deeper and advance integration, not just specifically livewire.

[@tariksadiku4723]

@@abuhurairah7042 Yeah, but if you know Vue, you automatically know other frameworks. That is not the case with Livewire.

[@BlackistedGod]

Its not a problem in Livewire per see, its the problem with people using framework/package not understanding how abstraction are done even the basics, like if you know HTML/CSS/JS, you would know toggle wouldn't need a goddamn server side call and can even be done in pure CSS. Ive never used Livewire but I did have a look at its docs, and it seems pretty simple and basic if you have solid knowledge of "web-based" programming This is why its very important to master a language and not a framework, If you can fully understand and master a specific language, you can work with any framework that are built on top of that language.

[@georgezimmer5622]

Livewire is fine, the issue I have with it is that it's marketed as an alternative to javascript when it's more an alternative to fetch. And the counter example they have on their getting started section is exactly a case where you should NOT use livewire for. You have to couple it with Alpine or Vanilla JS for cleint side interraction and Alpine can become disgusting really quick. That being said filament is incredibly usefull for low audience backoffice apps

[@JT-mr3db]

Livewire is mostly a complete PITA and my workplace have been slowly trying to eliminate it. If you are using alpine for any client side update then your full time job will be trying to make Livewire skip re rendering and you will have a mountain of tech debt in no time. For small projects where it’s mostly just you, it’s manageable, but in a team with a production grade product avoid it like the plague.

[@Voidstroyer]

Sounds like a really good use case for switching over to Elixir Phoenix with liveview.

[@JT-mr3db]

@ Elixir has come highly recommended, unfortunately we are far too late in the game to shift frameworks.

[@anasouardini]

Except for implementing PWA, Intertia just gives me all what I need.

[@lijahtech8200]

Is there a filament alternative for vue?

[@abuhurairah7042]

You could try nuxt. It has lots of modules that could have built something similar to what filament has

[@lijahtech8200]

@abuhurairah7042 interesting thanks, I've never worked with nuxt. I'll definitely try it out

[@underflowexception]

I think for hobby project/small projects livewire is OK but for serious projects it will break down.

[@abuhurairah7042]

I'm not a fan of "I think", and seriously your big projects would not break down just because you are using Livewire 😂

[@kuthub1989]

jQuery or Vue, I don't like in-between approach.

[@KevinLopez-rl6wq]

no HTMX plus Alpine.js?

[@kuthub1989]

@@KevinLopez-rl6wq no market for it.

[@scott_itall8638]

The inertia set up seems cumbersome.

[@gt6184]

Sorry can anyone just tell me (newB here) what it does better that react/next ??

[@abuhurairah7042]

if you're into js frameworks, try vue/nuxt

[@Voidstroyer]

Hard to say. But the biggest thing it does "differently" is giving you some more client side control without having to leave PHP. All is done from within Laravel. I guess that the biggest benefit is that because of this you don't need a separate API server. The server and the client are just one 1 project that use the same framework.

[@jaxxedbytes]

Both the thread and the video are lacking any real examples. Showing and hiding a button with Alpine sure is an example, but is def not a thing most people are worried about. Same with tables.