A question that may be a little silly but does these events would be replayable when time comes in ? ( in this case the time to hold item )
@cmorrell6 күн бұрын
Yep, in Verbs you can definitely replay events, and you can update how those events affect the State and use that new logic. If you watch my previous video on Verbs, there’s more focus on replay there.
@MarcoCarro18 күн бұрын
great video!
@dion310924 күн бұрын
Nice!
@SalvadorSánchez-n1b24 күн бұрын
thanx for explain
@ZahistaАй бұрын
this is nuts! :) I need to try it in some app! Thank you and Daniel! :)
@EserDenizАй бұрын
Great video! It’s cool to see more and more content about Verbs.
@jjjrmyАй бұрын
why can't this be done using actions instead? if we already have a bunch of actions I'd now have to move those into Verb Events instead?
@cmorrellАй бұрын
The upside of events over actions is that the event itself is stored in the db, rather than just the outcome of the event. If you’re already using the actions pattern, it’s relatively easy to switch to events, but it’s definitely work. Only you can decide if it’s worth it.
@jjjrmyАй бұрын
@@cmorrell it's not possible to have a trait for an action like "asVerb"? that way you don't have to change too much - or is that not possible based on how Verbs package works?
@cmorrellАй бұрын
That would be very cool! I’ve thought about it the other way-could Verbs work be routed to/etc like how Laravel-Actions works, but I never thought about it the other way around. I’ll have to tinker a bit to see what’s possible, but it’s a great idea!
@jjjrmyАй бұрын
@@cmorrell at least that way it's more the "Laravel way" and you can even turn built in actions (like Jetstream signup action) into a Verb without refactoring anything
@BenHolmenАй бұрын
Chris! This was such a chill pitch and it really resonated with me. Already wishing I would have written my last side project with Verbs. Maybe the next one!
@cmorrellАй бұрын
@@BenHolmen thanks Ben!
@christophrumpelАй бұрын
Great one 👏
@andrewpeacock5107Ай бұрын
Hi Chris, what's the app you're using at 11:43?
@cmorrellАй бұрын
@@andrewpeacock5107 that’s PhpStorm with the amazing Laravel IDEA plugin. It makes working with Laravel *so* good!
@andrewpeacock5107Ай бұрын
@@cmorrellAh, thanks.
@dion3109Ай бұрын
You are good at explaining! Really nice to watch. Hopefully you will be uploading frequently in the future. You can maybe make an video about every feature of Laravel. Like when to use observers, services etc
@kyledoesdevАй бұрын
great video!!!!
@nunomaduroАй бұрын
great video! thanks for this and for verbs. 🙌
@cmorrellАй бұрын
@@nunomaduro thanks for checking it out!
@SimonHampАй бұрын
great video, Chris! one day, my hair will also be this beautiful
@hayden_ellisАй бұрын
I agree with Josh's comment - this paints a nice picture of when to fire events and the upside of event sourcing. In my experience, when I'm trying to event source a particular feature, the biggest hurdle for me has been understanding how to use the state and models to store data as well as represent that data in the UI (and then updating/interacting with that data). And in Livewire, how to make it quick/snappy with Verbs.
@cmorrellАй бұрын
@@hayden_ellis yeah, I’m gonna try to make another video on state vs eloquent models. As for Livewire, that’s less my area of expertise. But I know Josh Hanley has done some talks about that-might want to look them up.
@joshcirreАй бұрын
This helped me a lot. I still haven't fully grasped when to use state vs. just models like you showed here. But this helped me see how events can be decoupled from state. Thank you!
@cmorrellАй бұрын
@@joshcirre I’ll see about making another video on State some time soon!
@AlbertCloete4 ай бұрын
When you're watching a podcast, do you have thoughts come up in your head about what you would say or ask if you were part of the conversation? Does that count as an internal monologue?
@AlbertCloete4 ай бұрын
I also won't use starter kits outside of the first party Laravel ones. I'm considering buying Mailcouch. A package like that, made by a trusted Laravel package creator, is something I might consider. So if your SaaS starter works like that, i.e. it's a package that I can install into my Laravel app, then I might buy it.
@KevinLopez-rl6wq4 ай бұрын
The JS ecosystem does have full stack solutions like AdonisJS, BlitzJS, and Redwood. It's just that not many people use them!
@paulrickett75645 ай бұрын
Why waste your time, move on from PHP and use Go.
@AlbertCloete5 ай бұрын
Really great discussion. I also prefer having more tickets in the sprint than I'd probably finish. But within reason. I think a goal of finishing 80% of the tickets in a sprint is good. It's good it have a goal and a stretch goal. The biggest pain point for me with the standard agile way of doing things is the sprint retro. I don't like coming up with "what went well; what can be improved" every two weeks. Usually after the 3rd or 4th sprint with a team, there isn't much left to discuss. I think it's good to have some team every two weeks where people can raise process issues they want to improve. But people shouldn't be forced to come up with issues. And yeah, the thought of deleting the backlog also gives me anxiety 😅
@Refresh54067 ай бұрын
Please ditch that Livewire nonsense. It's like the worst possible solution.
@blocSonic7 ай бұрын
As someone who has worked extensively within both the PHP / Laravel and JS (React/Vue/Astro) stacks, what PHP really needs is something much like Netlify that can grab a repo, then build & deploy an app super easily and with a predictable cost. For my laravel work, I've used Forge and Envoyer, while both are terrific they're tied to another SaaS product like Digitalocean for the server instances. It would be nice to see something like Netlify that handles all of that for PHP. If there is something like that (which there may be), I haven't come across it.
@romaric60229 ай бұрын
i think Blade fragments / HTMX is really underrated with laravel as a frontend !
@shofada8 ай бұрын
You are right. It works, it's simple, it feels natural
@eptic-c7 ай бұрын
I don't know if they fixed this but a big problem with fragments is if you have variables in the template that are not used in the fragment you need to provide those as well for the fragment to get rendered. So you can't use them as components, they might have fixed this idk