Symfony is my go to framework since I create long lifetime projects - many which exceed a decade of us. The long term support afforded by Symfony affords be the latest security patches for years (not months like Laravel) meaning I only need to perform major version upgrades to the framework less frequently saving time and money. When looking into a framework you’ll need to continue to support for many years, framework stability is huge.
That's really a rare and good thing to remember that in many cases ...we maybe don't actually need a Framework, but we just get used to it. A long way back, when trying to chose between Twig, Smarty &co some guy answered something like: "Why bloating your code with a templating library while PHP already do that natively?". He was not wrong but I was not ready, and busy to the "trendy things" at the moment, just like those that stuffed everybody into Laravel and coding more "Laravel" than actually PHP.
People keep sleeping on Spiral framework, but it's amazing. Docs are great, performance is top notch, and it's designed for mid-size to large-scale sites and promotes software engineering best practices all along the way.
I use CI because that's what the company has been using for past few years. Good information 👍. Would look forward to similar content on JS frameworks.
If working with PHP, i am keep in mind to use it as Backend. Sometimes i am using Slim, since it kind like express in NodeJS, i can setup the folder dir with my own preference.
I thought I had mentioned Fat-Free, I guess not. I have used it in the past and you are correct, it is a great one to use on personal projects. Once you get to larger requirements, I would switch to one of the bigs ones.
I honestly disagree with the suggestion for people who have exposure to MVC to use Laravel over Symfony; Laravel's implementation of MVC is a mess, and their documentation does not help. If your requirements are EXTREMELY simple, or you are already an experienced Laravel user this isn't a problem, but if your trying to implement business logic based on the MVC design patten for the first time, Symfony is a vastly cleaner option (at least at time of writing).
I think the opposite in some ways, maybe it is just personal preference though. For me, Laravel's documentation is easier to use and understand especially if you are just starting or even if you have experience with other MVCs. Laravel is a quick and easy way to get into MVC development. Again, this may be personal bias. I do agree with your interpretation of rapid application development vs business application. Symfony would be better for larger, more business-oriented projects since it is a more long-term solution whereas Laravel would help smaller projects get off the ground quicker. Not necessarily "EXTREMELY" simple projects but smaller nonetheless. I think the biggest difference between these two are personal preferences for the most part. This argument has been going on since Laravel came out and you would have some devs that swear by Laravel and others that swear by Symfony. I got into Laravel development early on and I liked it so it is my go-to over Symfony, but Symfony has its place when I am working with a bigger, more well-rounded infrastructure and Laravel is not already being used. Lastly, Laravel uses a lot of Symfony's components so switching between the two is not a huge hurdle, it just depends on the situation for you at the time of development. My 2 cents at least.
Hello, what about Nicotine Framework for PHP & MySQL? It is very fast, has support for Admin, API requests, CLI cronjobs and it is modern, works with PHP >= 8.2.0
I thought i did. I would say, use it in the same places where you use Laravel since Laravel is based on it. Both great mid-level to high-level frameworks.
@@DevDrawer lol, I mean that I keep hearing "twenty-twenty-thirty" rather than "twenty-twenty-three". Anyhow, it's probably just me, automatic subs transcribe it as 2023.
@DevDrawer For sure, that got my attention. In the end, I think I'll use Symfony since I'm familiar with it as I am a Drupal developer. The fun part is that I already used it without knowing. 😅
They are built using the code they eventually become a framework for. A framework is simply a codebase that utilizes existing functions and create components for them in a way that is easier to use for the end user. You could write a new framework specifically for yourself to use by creating resuable components for certain things you would like to do easier using the parent codebase. For these examples, they are just fleshed out resources to speed up PHP development so you don't have to worry about certain things if you use built-in components created for this purpose.
I have never used it before. It looks similiar to the other frameworks I have listed. On their website, they say it is much faster though. What are your thoughts on it?
Symfony is my go to framework since I create long lifetime projects - many which exceed a decade of us. The long term support afforded by Symfony affords be the latest security patches for years (not months like Laravel) meaning I only need to perform major version upgrades to the framework less frequently saving time and money. When looking into a framework you’ll need to continue to support for many years, framework stability is huge.
I agree. Symfony is a great option for lifetime projects.
Sir any recommended symfony tutorial?
That's really a rare and good thing to remember that in many cases ...we maybe don't actually need a Framework, but we just get used to it. A long way back, when trying to chose between Twig, Smarty &co some guy answered something like: "Why bloating your code with a templating library while PHP already do that natively?". He was not wrong but I was not ready, and busy to the "trendy things" at the moment, just like those that stuffed everybody into Laravel and coding more "Laravel" than actually PHP.
Well said
People keep sleeping on Spiral framework, but it's amazing.
Docs are great, performance is top notch, and it's designed for mid-size to large-scale sites and promotes software engineering best practices all along the way.
I'm gonna have to take a look at it. I have never heard of Spiral.
I use CI because that's what the company has been using for past few years.
Good information 👍.
Would look forward to similar content on JS frameworks.
Thanks for watching. CI is good too. I will try to do one of these for JS too. Thanks for the tip.
TRONGATE is like CI on steroids....in fact, its nothing like CI....because its STABLE FROM THE GROUND UP! CI is dead, use TRONGATE!!!!
I've been using fuelphp since 2014, I really like it, it's fast and has a lot of features.
That's great. It is a good one.
If working with PHP, i am keep in mind to use it as Backend. Sometimes i am using Slim, since it kind like express in NodeJS, i can setup the folder dir with my own preference.
Also small and fastest
Always. PHP should not be mixed in with frontend code if at all possible.
Fantastic content-rich and exactly what I was looking for, cheers!
Good to hear. Glad you liked it.
CI is the fastest in terms of execution
I would only use CI for anything serious that needs to be maintained.
You should have add Trongate.
I keep hearing about Trongate. I am gonna have to check it out in more detail.
Any recommended symfony tutorial?
For personal projects I use F3.
I thought I had mentioned Fat-Free, I guess not. I have used it in the past and you are correct, it is a great one to use on personal projects. Once you get to larger requirements, I would switch to one of the bigs ones.
Codeigniter period.
I honestly disagree with the suggestion for people who have exposure to MVC to use Laravel over Symfony; Laravel's implementation of MVC is a mess, and their documentation does not help. If your requirements are EXTREMELY simple, or you are already an experienced Laravel user this isn't a problem, but if your trying to implement business logic based on the MVC design patten for the first time, Symfony is a vastly cleaner option (at least at time of writing).
I think the opposite in some ways, maybe it is just personal preference though. For me, Laravel's documentation is easier to use and understand especially if you are just starting or even if you have experience with other MVCs. Laravel is a quick and easy way to get into MVC development. Again, this may be personal bias.
I do agree with your interpretation of rapid application development vs business application. Symfony would be better for larger, more business-oriented projects since it is a more long-term solution whereas Laravel would help smaller projects get off the ground quicker. Not necessarily "EXTREMELY" simple projects but smaller nonetheless.
I think the biggest difference between these two are personal preferences for the most part. This argument has been going on since Laravel came out and you would have some devs that swear by Laravel and others that swear by Symfony. I got into Laravel development early on and I liked it so it is my go-to over Symfony, but Symfony has its place when I am working with a bigger, more well-rounded infrastructure and Laravel is not already being used.
Lastly, Laravel uses a lot of Symfony's components so switching between the two is not a huge hurdle, it just depends on the situation for you at the time of development. My 2 cents at least.
Which PHP framework do you use? Why or why not?
For me Symfony and it is hard to for beginners. 😅
I tend to agree. My go-to is still Laravel. I gotta check out some of these other frameworks people are mentioning.
Hello, what about Nicotine Framework for PHP & MySQL? It is very fast, has support for Admin, API requests, CLI cronjobs and it is modern, works with PHP >= 8.2.0
I have never heard of this one. I'll take a look.
Thank you, Great understandable video.
What about Symfony you didn't mention in which cases we should use it :)
I thought i did. I would say, use it in the same places where you use Laravel since Laravel is based on it. Both great mid-level to high-level frameworks.
Laravel is my favorite one, but with any new versions he become more complicated, and this is not good...
I agree but it is better to know it than not to. I listed that as a con as a lot of devs feel the same way.
I went to Yii2 from alarmbel, and love it even it’s less popular.
We need a drupal development course from you plz!
Hey, sorry about this. I don't work with Drupal so I don't know too much about it outside of its existence.
00:04 - I'm not native, but... Did you say: "framworks you should use in 202030"?
2023 or 20 20 3. I can see how that sounds weird but I believe I said the year.
@@DevDrawer lol, I mean that I keep hearing "twenty-twenty-thirty" rather than "twenty-twenty-three". Anyhow, it's probably just me, automatic subs transcribe it as 2023.
lol, well that may be due to my very southern accent. I have been told my accent is very apparent. I don't hear it, but other people do, I guess. 😂
@DevDrawer
For sure, that got my attention. In the end, I think I'll use Symfony since I'm familiar with it as I am a Drupal developer. The fun part is that I already used it without knowing. 😅
Awesome to hear
How are frameworks built?
They are built using the code they eventually become a framework for. A framework is simply a codebase that utilizes existing functions and create components for them in a way that is easier to use for the end user. You could write a new framework specifically for yourself to use by creating resuable components for certain things you would like to do easier using the parent codebase.
For these examples, they are just fleshed out resources to speed up PHP development so you don't have to worry about certain things if you use built-in components created for this purpose.
slimphp, twig, phpleague, etc
Great suggestions. Thank you.
Laravel kills all! 😊
The others have their place, but Laravel is awesome.
What about Trongate PHP?
I have never used it before. It looks similiar to the other frameworks I have listed. On their website, they say it is much faster though. What are your thoughts on it?
@@DevDrawer It's really seriously, ridiculously fast. Absolutely bonkers, and doesn't get in your way.
Still love Yii2
I have never used it but it does look interesting for smaller projects.
we use yii3, it seems a mistake😂
ViperPHP 😂
I have never used that one. Is it any good?
@@DevDrawer I think it is a minimized version of Codeigniter, simpler, cleaner, and considerable for small project.
Cool. I will take a look at it. I love simpler and cleaner.