I thought so, too, but after creating a few videos and tweeting about that RILT stack, it doesn't seem to get much traction or engagement at the moment. Maaaaaybe in 2025 something will change. But I would not use the work "skyrocket" here :)
Goodmorning Sir, Respect from India.. "How can I resolve the issue where data entered by User A (HR role) is showing up in User B's (HR role) account, even though they are using different email IDs? Both users are assigned the HR role, and the data should be segregated."
It's mostly for people who are heavily into Laravel and the way Laravel does things For me it's much easier because I just make blades and php "controller/component" type files and it just... Works. No typescript, relearning, or other structuring needed Anyone who thinks they need to write a bunch of JavaScript isn't doing Livewire right Also don't need to use vite or build, etc etc lol
Those are people who never were into JavaScript anyway and they prefer to continue writing code in Laravel way (Livewire is basically the same syntax) without diving deep into NPMs, VITEs and other complex stuff. Also, Livewire tends to be better for smaller projects, for rapid development, with not that many interactive components.
Like the others said, but also you are staying in pure PHP and getting the benefits of how much easier debugging it is (in my opinion), rather than worrying about checking the inspect element console for JS errors etc, if an exception occurs while developing it will nicely break and show you in Laravel's built in way with stack tracing etc. Without having to guess whether the issue originated somewhere on the Vue / JS side or in PHP.
I'm rooting for Livewire/Volt!
I think React with inertia and Laravel will skyrocket in 2025...
Nah lol
I thought so, too, but after creating a few videos and tweeting about that RILT stack, it doesn't seem to get much traction or engagement at the moment.
Maaaaaybe in 2025 something will change. But I would not use the work "skyrocket" here :)
Good summary of Laravel Key Updates 👏 Hoping to see more updates from You! Keep Going 🙌
Reverb?
Damn, I always thought Reverb was released in 2023. But you're right, it's February of 2024, how could I miss this.
Goodmorning Sir,
Respect from India..
"How can I resolve the issue where data entered by User A (HR role) is showing up in User B's (HR role) account, even though they are using different email IDs? Both users are assigned the HR role, and the data should be segregated."
i don't understand how people like livewire over vue or or react
It's mostly for people who are heavily into Laravel and the way Laravel does things
For me it's much easier because I just make blades and php "controller/component" type files and it just... Works. No typescript, relearning, or other structuring needed
Anyone who thinks they need to write a bunch of JavaScript isn't doing Livewire right
Also don't need to use vite or build, etc etc lol
This is why 👐 @@JamesAutoDude
Those are people who never were into JavaScript anyway and they prefer to continue writing code in Laravel way (Livewire is basically the same syntax) without diving deep into NPMs, VITEs and other complex stuff.
Also, Livewire tends to be better for smaller projects, for rapid development, with not that many interactive components.
Like the others said, but also you are staying in pure PHP and getting the benefits of how much easier debugging it is (in my opinion), rather than worrying about checking the inspect element console for JS errors etc, if an exception occurs while developing it will nicely break and show you in Laravel's built in way with stack tracing etc. Without having to guess whether the issue originated somewhere on the Vue / JS side or in PHP.
@ZephniStrife that's true! Never thought of that since I've always relied on Livewire, but you're right, it's so much easier to debug forsure