Maybe this will be weird, but YAY ADS! I'm not being sarcastic - getting sponsorships increases the likelihood that we will continue seeing this amazing well-crafted content and I'm stoked for that ❤ Also, thank you both for another great video!
I'm a 41 years old guy, I started programming in PHP with 16 years old, landed my first job as a programer at 21, I did amazing thing with PHP. Now, it's been almost 12 years that I don't use it anymore, but my brain still finds it easier to learn thing in PHP than using my current stack, funny how that works....
Even though many people hate or make fun of PHP, I still think modern PHP doesn't need to shy away from competition. I have a similar vita as you, and while I often use Go for new projects, coming back to PHP and especially Laravel or Symfony is a joy. And with Octane, you can even combine PHP with Go.
@@aarondfrancis I wish I could, I didn’t wanted to stop using it, it’s just the industry, hype, whatever you want to call it. Never the less I still enjoy the content, core concepts such as IoC, are transferable to any tool, so let’s keep at it!
Awesome content Aaron 👍 Your super educational way of teaching got me into php and Laravel after years of hesitating to try it, and now there is no way back. Thanks for sharing your knowledge mate ♥
Ha, yeah if your system is very simple and Laravel only this is kinda cool. As soon as you have heterogeneous systems that need to work together this simple, free solution will fall down
Currently building a quite complex meta search engine and Laravel makes it so easy. Probably launching production this year. If i did it in another stack it'd probably take me more than a year
"That seems....pretty ~dumb~" - Aaron Francis, looking at his own code. Love the video! Bookmarking literally all of these to send to people when they ask me why I still use PHP/Laravel in 2024
Aaron, a tip for the artisan cli: if you type `artisan ` you will get all the commands in that namespace. For a shorter display you can make it error out adding the : after the namespace.
If not because of subscribing to you, i would not have known about this neat feature flags in laravel. I usually use spatie permission and sometimes it just too granullar for my use cases, maybe the thing i need for my past projects was this feature flags. Thank you Aaron! Maybe for future topics, is there an Alert System in Laravel to notify developer if some user encounter error in their production apps? Keep up the good works, your videos is very pleasant to hear!
Pennant looks great. The problem I have with feature flags is that people abuse it. I have seen codebase with hundreds of feature flags, a thousands of dead lines of code, never been deployed/used. Also I have seen deployments failing because of too many if/then. Because when you develop a feature you have code regarding that feature everywhere. So feature flags should be only used when strictly necessary,, and not as development approach. Having only the master branch and relaying exclusively on feature flags is a (very) bad idea. Trunk development is a bad idea. Use branches, gitflow, and eventually feature flags, when you are rolling out features that require to be tested by a restricted number of users. This is not the case for all the features, this is the case for just a small percentage of you develop. Abusing feature flags will make your code unreadable. Also flags should be removed when the feature is released for all. Does Pennant have something for that?
Both gitflow and trunk based development have their own tradeoffs, as everything in programming. I worked with both patterns and cannot really decide which one I like more. Although I do have to agree feature flags do get abused a lot in trunk development. People are like "Oh I have to change this page title to say something else, I'll put it behind a feature flag" and proceed to create a feature flag for most useless of things. Hiding larger features or chunks of logic behind feature flags I think is nice, but going too granular is a maintenance nightmare. I've seen people introduce feature flags into code only to remove them literally 24-48 hours later, which is pointless and just unnecessary overhead.
Hi Aaron, me too I prefer light mode to work but I find that dark mode more versatile for videos for two reasons: first, white is too bright when watching at night 😅 and two, switching from full frame video to white editor is too harsh. Anyway, just my 2 cents. Keep up the good work.
These videos make me want to use Laravel more and more. I wonder how hard it’d be to swap now. I have been working on a Vue 3 front end and just started the backend portion. Express is proving to be a headache for logging in with Steam 💀 I might have to learn more and see if this is the perfect fit, I’m just not too sure how to best connect existing data or if I can define models for an existing schema. I’ll have to investigate 🕵️♂️
If you just started working on your backend and didn't do much work, just switch to Laravel. In Express you'll end up connecting 10 different libraries for things that Laravel provides out of the box and that all integrate nicely in Laravel because they are officially supported. And also Express is outdated and isn't really maintained for a few years now.
Hmmm I don't know if I've ever seen anyone use Pennant for that. I bet you could make it work, but it feels like a little bit of an unsupported use case
Maybe this will be weird, but YAY ADS! I'm not being sarcastic - getting sponsorships increases the likelihood that we will continue seeing this amazing well-crafted content and I'm stoked for that ❤
Also, thank you both for another great video!
Whew 🥰 wasn't expecting that!
And he should now get some sleep. I could see how tired he was. Maybe it was just me.
@@brianochieng5904 might be the whole dad of many kids thing 😂 I saw him taking a nap at a play center once on Twitter 😁
🎯
Really enjoying your way of teaching!!
I'm a 41 years old guy, I started programming in PHP with 16 years old, landed my first job as a programer at 21, I did amazing thing with PHP. Now, it's been almost 12 years that I don't use it anymore, but my brain still finds it easier to learn thing in PHP than using my current stack, funny how that works....
Come back! Join us!
Even though many people hate or make fun of PHP, I still think modern PHP doesn't need to shy away from competition. I have a similar vita as you, and while I often use Go for new projects, coming back to PHP and especially Laravel or Symfony is a joy. And with Octane, you can even combine PHP with Go.
12 years using most php hoping that will get better. And here we are.
45 here started with php at 19 and still at it. People have been telling me it was a dead language since I was 25
@@aarondfrancis I wish I could, I didn’t wanted to stop using it, it’s just the industry, hype, whatever you want to call it. Never the less I still enjoy the content, core concepts such as IoC, are transferable to any tool, so let’s keep at it!
Awesome content Aaron 👍 Your super educational way of teaching got me into php and Laravel after years of hesitating to try it, and now there is no way back. Thanks for sharing your knowledge mate ♥
You're welcome! Thanks for saying so
First party? That's sucks. I wanna pay $20 per month for SaaS subscription to do that.
😂
Ha, yeah if your system is very simple and Laravel only this is kinda cool. As soon as you have heterogeneous systems that need to work together this simple, free solution will fall down
Or you can write your own storage driver! Honestly just using the database driver is probably good enough. You can read it from anywhere
A subscription and a network dependency (point of failure)
I’m so glad to see you making content on your own channel. To the moon my friend, to the moon!
Thank you! 🚀👨🚀
Another banger, though dark mode would make it a lot easier to watch at night 🔥👀
Lower your brightness
Currently building a quite complex meta search engine and Laravel makes it so easy. Probably launching production this year. If i did it in another stack it'd probably take me more than a year
🥰
Woah .. this is so much better than what I have had to do in Node.js and Next.js applications!!
Simply so great and clearly explained! Thank you!
It's great to have first-party FF, nice video man.
"That seems....pretty ~dumb~" - Aaron Francis, looking at his own code.
Love the video! Bookmarking literally all of these to send to people when they ask me why I still use PHP/Laravel in 2024
Hahaha I wrote that code and that was my immediate, unfiltered thought 😂
Aaron, a tip for the artisan cli: if you type `artisan ` you will get all the commands in that namespace. For a shorter display you can make it error out adding the : after the namespace.
Oh nice! Smart
@@aarondfrancis The Laravel team thought of everything!
If not because of subscribing to you, i would not have known about this neat feature flags in laravel. I usually use spatie permission and sometimes it just too granullar for my use cases, maybe the thing i need for my past projects was this feature flags. Thank you Aaron!
Maybe for future topics, is there an Alert System in Laravel to notify developer if some user encounter error in their production apps?
Keep up the good works, your videos is very pleasant to hear!
Thank you so much!
You rock Aaron!
I don't use Laravel, and last time I touched PHP was over 6 years ago... Why am I here? 😂
PS: Awesome video, as always! 😊
We'll get you back!
@@aarondfrancis I wouldn't mind, I heard you guys have Lambos! 😆
Thanks for sharing!
awesome video!
Pennant looks great. The problem I have with feature flags is that people abuse it. I have seen codebase with hundreds of feature flags, a thousands of dead lines of code, never been deployed/used. Also I have seen deployments failing because of too many if/then. Because when you develop a feature you have code regarding that feature everywhere. So feature flags should be only used when strictly necessary,, and not as development approach. Having only the master branch and relaying exclusively on feature flags is a (very) bad idea. Trunk development is a bad idea. Use branches, gitflow, and eventually feature flags, when you are rolling out features that require to be tested by a restricted number of users. This is not the case for all the features, this is the case for just a small percentage of you develop. Abusing feature flags will make your code unreadable. Also flags should be removed when the feature is released for all. Does Pennant have something for that?
Both gitflow and trunk based development have their own tradeoffs, as everything in programming. I worked with both patterns and cannot really decide which one I like more. Although I do have to agree feature flags do get abused a lot in trunk development. People are like "Oh I have to change this page title to say something else, I'll put it behind a feature flag" and proceed to create a feature flag for most useless of things. Hiding larger features or chunks of logic behind feature flags I think is nice, but going too granular is a maintenance nightmare.
I've seen people introduce feature flags into code only to remove them literally 24-48 hours later, which is pointless and just unnecessary overhead.
Hi Aaron, me too I prefer light mode to work but I find that dark mode more versatile for videos for two reasons: first, white is too bright when watching at night 😅 and two, switching from full frame video to white editor is too harsh. Anyway, just my 2 cents. Keep up the good work.
You can lower your brightness.
Can you sometimes share your PHP Storm config? Looks pretty neat.
These videos make me want to use Laravel more and more. I wonder how hard it’d be to swap now. I have been working on a Vue 3 front end and just started the backend portion. Express is proving to be a headache for logging in with Steam 💀
I might have to learn more and see if this is the perfect fit, I’m just not too sure how to best connect existing data or if I can define models for an existing schema. I’ll have to investigate 🕵️♂️
You might like this video, particularly the inertia part! th-cam.com/video/gRtv-BVkwA4/w-d-xo.html
If you just started working on your backend and didn't do much work, just switch to Laravel. In Express you'll end up connecting 10 different libraries for things that Laravel provides out of the box and that all integrate nicely in Laravel because they are officially supported. And also Express is outdated and isn't really maintained for a few years now.
I'm curious what is the Database management tool you use in this video?
Is that DB Browser?
He’s using TablePlus
@@alcymn Thank you 🥰
What's the name of white theme of phpstorm? I liked it.
Can you do the same thing with Gates?
Maybe! Not super sure.
Sneaky finger at 5:23 😋
oopsie doopsie
Great! Would this also be recommended for user preferences that they choose themselves?
Hmmm I don't know if I've ever seen anyone use Pennant for that. I bet you could make it work, but it feels like a little bit of an unsupported use case
@@aarondfrancis cool, I'll look into it. I'm new to Laravel. Thank you for the reply! I love your content! ❤️
Do we have any good lsp of laravel for vscode?
light theme was a horrible idea
Besides that, what'd you think
I'm thinking why do we actually need that feature?
You might not
light theme console? you must be a psycho :D
k
okay, but why light mode ?
same reason I do almost everything I do: I like it
@@aarondfrancis Finally found someone who is not trend-driven👍
Because he wants this information to be seared into your retinas so you retain it
first
i like the way you make the explanations more easier
Thanks