You could probably send a notification when the user (for instance the admin of the meetup you used as an example) is logged in. If he/She is not logged in, then you send an e-mail.
at the end you said it comes down to your personal preference, but a common scenario is giving the user the choice of how they want to receive the notification. So the user could manage their preferences and say, notify me by email, by text, or a daily digest (for example), or all three. Notifications handles all this so if you chose mailable initially, you would need to convert it over.
Personally when I just need to send email I use email, you have more flexibility(Multiple receivers, add cc, bcc and more...) Notification is good when you can for example to show the user list of notifications(using DB), send SMS or slack message
Thank you. Great content as always. One thing I'd probably include on the notification email is the meetup name so such cases where a user (organizer) has multiple meetups would know which of them a new registrant has signed up for.
You are the best. You turned me on to Livewire. Wish it was covered more on RU-vid than people getting so excited that they can continue the JavaScript ecosystem mess to Laravel with IntertiaJS. No hate though. That is awesome too. I am student and have published some stuff, but watching you write Livewire is such a breath of fresh air. Go make stuff!
Hey i really enjoyed this video. I personally always reach for notifications rather than mailables. It's a habit I developed from my job but carried over into my personal projects.
Thanks for watching Kyle! Yeah, I didn't even know for the longest time that notifications could be emails too, but now I'm reaching for them more and more. :) -Josh
Hey there! Thanks for watching and glad that it could be helpful in explaining it. :) This is VSCode with the TALL Stack plugin pack and PHP Intelephense (can't wait for the VSCode Laravel plugin). -Josh
Great tutorial videos, thanks. Could you please try to normalize or master your voice audio track in your future videos, because it currently sounds relatively soft, which requires some extra focus and volume to clearly understand your explanation. Nothing wrong with your content or attitude, thanks again for these Laravel related tutorials!
Hey there, I'll try to do better at fixing this in the future. I haven't gotten too many comments about it since some of the older videos weren't as good, but I'll try to keep an eye on it! -Josh
@@LaravelPHPit’s just how you speak, you tend to drop your vocal inflection at the end of your sentences and interestingly when you look away from the camera but frankly it’s quite subtle and likely the original commenter’s hardware is more to blame than anything you’re doing. It’s definitely deep in the nitpick zone 😂 Nice vid sir
I don't want to sound like I invalidate your experience, but I find his voice very pleasant. Usually streamers talk too loud for my taste and his voice here I find very calming.
@keithprinkey8575 0 seconds ago It looks like Laravel is moving towards a more paid model, which could put developers in a tough spot. Some of their first-party packages, like Laravel Nova and Spark, are already behind paywalls. Laravel Herd, while free to download, doesn’t offer much beyond providing a simple web server-something developers could easily set up themselves with open-source tools like nginx or Apache. So why should we pay Laravel for something as basic as local hosting, other than for convenience? Sure, a company needs to be profitable, but wasn’t Laravel supposed to be open source? If Taylor Otwell and Laravel were truly committed to open source, why are they monetizing more and more aspects of the ecosystem? Laravel Herd, for example, only offers nginx and DNSmasq for free-both of which are open source anyway. It seems like another case of taking open-source software and slapping a price tag on it down the road. This isn’t even counting the other first-party paid packages that Laravel offers. In the true spirit of open source, companies typically receive funding from their communities to maintain the codebase, rather than making users pay for core tools. Then there’s the $54 million in funding Laravel received. It’s hard to believe they just handed over that money without expecting anything in return. It raises questions about whether Laravel is slowly shifting from being open source to becoming a paid ecosystem. This shift could be problematic for the open-source community. Companies like Laravel often start out open source, but as soon as they gain traction or funding, they begin monetizing everything. No matter what’s been said, Laravel could be on the path to becoming a paid product soon enough-especially since they’re already charging for services like Laravel Cloud.
It looks like Laravel is moving towards a more paid model, which could put developers in a tough spot. Some of their first-party packages, like Laravel Nova and Spark, are already behind paywalls. Laravel Herd, while free to download, doesn’t offer much beyond providing a simple web server-something developers could easily set up themselves with open-source tools like nginx or Apache. So why should we pay Laravel for something as basic as local hosting, other than for convenience? Sure, a company needs to be profitable, but wasn’t Laravel supposed to be open source? If Taylor Otwell and Laravel were truly committed to open source, why are they monetizing more and more aspects of the ecosystem? Laravel Herd, for example, only offers nginx and DNSmasq for free-both of which are open source anyway. It seems like another case of taking open-source software and slapping a price tag on it down the road. This isn’t even counting the other first-party paid packages that Laravel offers. In the true spirit of open source, companies typically receive funding from their communities to maintain the codebase, rather than making users pay for core tools. Then there’s the $54 million in funding Laravel received. It’s hard to believe they just handed over that money without expecting anything in return. It raises questions about whether Laravel is slowly shifting from being open source to becoming a paid ecosystem. This shift could be problematic for the open-source community. Companies like Laravel often start out open source, but as soon as they gain traction or funding, they begin monetizing everything. No matter what’s been said, Laravel could be on the path to becoming a paid product soon enough-especially since they’re already charging for services like Laravel Cloud.
That's the problem with frameworks. It's all about the developers that want to become "famous". Who in their right mind uses Laravel for a greenfields project 🙄
Well PHP people are nice because they don't have superiority complex...especially when their language is wrongly accused of being inferior. We just ship! #phplife
As a TypeScript developer, I'm surprised I haven't heard more about Inertia. As I continue to learn about it, it really seems amazing! I think I'm going to be switching from Node and React to Laravel/Rails, Inertia, and Vue/Svelte.
Thats great, but can u answer a few questions? 1. What is this editor? 2. And this question is leads from above one. Is there any way to use highlightings, suggestions and completions? Like in your editor? It's only thing that holds me from switching to volt from traditional way. Anyway, great video and great vocal for explanation and education :)
After years of being a hobbyist in Laravel (been a pro web dev for over two decades) i landed a role as a Laravel specialist over a year and a half ago. I hope to eventually do Laravel consulting, I'm just all in on the framework, the ecosystem, the community, the superpowers it gives me and my team.
I don't think it's good having a face of someone specific in front a big project like this with the feeling of "this person runs it all alone". Don't get me wrong, I'm just a noob, but I like the feeling of having an entire community behind it. If it's already like it is to Laravel, the message didn't get to me yet. In that case, pardon me.
The only thing that I expect from laravel cloud is they don't use a cloud provider, I want they purchase their own servers and go to the data centers and put them there so we can ski the big overprice of cloud
