Thanks a lot for this project. I work with Vue/Laravel stack. I was Vue.js developer first, and then added Lavarel. I think both work extraordinary well together, and the sintaxis of both is very similar. Again, thanks bro. Blessings from Venezuela.
I miss this community and Laravel. I got a job four different times from this channel and the courses. Been busy with work and haven't been watching any videos for a couple weeks. Current job is Senior Developer with Yii 1. I'm having physical withdraws from it not being Laravel
I used live wire for my project but decided to refactor into inertia + react. Live wire seems like it is sending so much traffic roundtrip and processing everything on the backend seems like it is expensive for cpu cycles. I’m sure Alpine helps, but we ended up going with React.
Most of the job market is covered by existing projects to be honest, Livewire is my prime choice for new projects and they have Flux as well which is very useful
It's hard to measure the performance on this relatively small project. But you can take the GitHub repo and try it yourself if you want. Or maybe we will do separate experiments in the future when we have more free time.
Hard to measure in our small application. Creating a bigger one could show more advantages/disadvantages for each one. If talking strictly about "how it felt" - in this app, it was pretty even. Bigger apps might have different stories :)
If you talk about requests/s react and Vue are the same since it's the same backend. So it's about livewire Vs Vue/react. You'd have to create a production env with web servers capable of doing concurrent requests ie nginx and Apache. Artisan serve is single threaded. But that doesn't tell you much. A lot depends on other architecture choices like caching, load balancing etc.
I guess what's asked in jobs lags behind what's trending. And for Devs it's wishful thinking. What they want to work with is not always what's possible at a job, existing Devs and projects usually dictates what you'll be using.
In this case, these are way too simple to tell the whole story. Let's say they are all equal in our demo application - that would give the wrong message that it has no performance differences, while in bigger applications - that might not be the case.
amazing to see vue take a lead over that of react, I would have thouht it to be the other way round for jobs at least livewrire is the winner for me in terms of effectivity and productivity particulry in the MVP space, there after I might consider vue now over react as I prefer vue to work with but am surprised to see its increased popularity in the job market
Laravel + Livewire ❤
Thanks a lot for this project.
I work with Vue/Laravel stack. I was Vue.js developer first, and then added Lavarel.
I think both work extraordinary well together, and the sintaxis of both is very similar.
Again, thanks bro. Blessings from Venezuela.
I miss this community and Laravel. I got a job four different times from this channel and the courses. Been busy with work and haven't been watching any videos for a couple weeks. Current job is Senior Developer with Yii 1. I'm having physical withdraws from it not being Laravel
I used live wire for my project but decided to refactor into inertia + react. Live wire seems like it is sending so much traffic roundtrip and processing everything on the backend seems like it is expensive for cpu cycles. I’m sure Alpine helps, but we ended up going with React.
Biggest selling point for Livewire for me is test convenience. Testing feels way less painful.
Thanks a lot for this, I’ve been pondering on this for some time now
Most of the job market is covered by existing projects to be honest, Livewire is my prime choice for new projects and they have Flux as well which is very useful
I use Livewire for projects that will be deployed on shared hosting and Angular+Laravel API for projects that will be deployed on the cloud
shared hosting sucks especially with Laravel or Symfony
Livewire is pretty clean and short. The performance is also great, as i am working on small project with 100,000 rows, pretty fast
It's ok, but when you have a lot of users and more complex logic, it is better to use the frontend so backend does not have a lot of work.
@@nadjimmalade2847 Well, don't forget to have a good performance, you have a good backend, since the performance comes from backend.
how about the performance diff?
It's hard to measure the performance on this relatively small project. But you can take the GitHub repo and try it yourself if you want. Or maybe we will do separate experiments in the future when we have more free time.
Hard to measure in our small application. Creating a bigger one could show more advantages/disadvantages for each one. If talking strictly about "how it felt" - in this app, it was pretty even. Bigger apps might have different stories :)
If you talk about requests/s react and Vue are the same since it's the same backend. So it's about livewire Vs Vue/react.
You'd have to create a production env with web servers capable of doing concurrent requests ie nginx and Apache. Artisan serve is single threaded.
But that doesn't tell you much. A lot depends on other architecture choices like caching, load balancing etc.
Also depends on the client, sometimes it's faster to calculate stuff on the server than in the browser
@@rutgerhoutdijk3547 It tinks it better to load data with server and for some calculations, let the brosser do that.
Laravel + Inertia (React) ♥
I guess what's asked in jobs lags behind what's trending. And for Devs it's wishful thinking. What they want to work with is not always what's possible at a job, existing Devs and projects usually dictates what you'll be using.
What are their lighthouse performance scores?
In this case, these are way too simple to tell the whole story. Let's say they are all equal in our demo application - that would give the wrong message that it has no performance differences, while in bigger applications - that might not be the case.
amazing to see vue take a lead over that of react, I would have thouht it to be the other way round for jobs at least
livewrire is the winner for me in terms of effectivity and productivity particulry in the MVP space, there after I might consider vue now over react as I prefer vue to work with but am surprised to see its increased popularity in the job market
Thank you, good jop!
Would have liked to see info about package size etc
Package size? What do you call package in this case?
Would you make a video on Nuxt with Laravel?
Nuxt is the backend for Vue, why would you use it with Laravel?
@@scott_itall8638 wouldn't call it like that
yes please
@@scott_itall8638 What are you talking about? Nuxt is NOT a backend for Vue, it is a frontend meta-framework. I use Nuxt with Laravel all the time.
@@scott_itall8638 What are you talking about? Nuxt is NOT a backend for Vue, it is a frontend meta-framework. I use Nuxt with Laravel all the time.
i prefer Svelte + Inertia