Passionate generalist conquering the web one project at a time. Whether authoring libraries for node, JS, PHP, or Rust, I am always on the lookout for better solutions to common problems.
Location
USA
Work
Lead Developer & Co-founder at corpscrypt, CTO at REtech
I really don't know what inspired this article, but I will have to try to keep my response as professional as possible, given how I feel about it.
Ignoring the click-baity title, the content itself is borderline propaganda. And I say that as someone who has a lot of respect for the technology in question and even regard it as one of the best frameworks myself.
Due to the enormous demand for online applications and server-side scripting, PHP has undoubtedly become one of the most popular languages in recent years
As much as I wish that was true, this is simply wrong. PHP has dominated backend-development for decades but has lost popularity in recent years, despite very magnificent improvements.
This article will go over the features of Laravel that have led to it being regarded as the best PHP framework.
This type of language is referred to as "lost speaker". If you were to ask "by whom is it regarded as the best PHP framework", you would quickly figure out that nobody is willing to say that. The reason for this is that experienced developers would hesitate to say something like "x is the best framework" as it always depends on the use-case. In my experience, whenever you hear someone say "x is the best framework" it usually means "x is the only framework I am comfortable working with".
Despite ranking 7 on PHP Benchmarks' list of top-performing web development PHP frameworks, it tops our list due to its large community, rich feature set, and ease of use.
For the reader: OP is likely referring to a particular benchmarking website phpbenchmaks. As of the time of writing this, the website lists a total of 7 PHP frameworks. So saying that it ranked 7th is very misleading as it distorts the fact that laravel ranks last in this particular benchmark comparison. It should be noted that there are countless different ways to benchmark performance and that there is only so much any benchmark test reveals about real-world performance, but this would be a topic within itself.
Laravel is a free and open-source web development framework. You do not have to pay any licence fees to use Laravel.
As compared to which framework? While proprietary frameworks exist, they are so rare that saying that all frameworks are open source and free is closer to the truth.
Everything in Laravel is documented, It also has API documentation with lists of all the classes and methods declared in Laravel to enable you to follow the right naming conventions. Everything you need to get you off the hook is available in the documentation.
Again, which framework doesn't have elaborate documentation? Don't get me wrong, laravel has an exceptionally beautiful and nice to navigate documentation, but the way this is described makes it sound as this wouldn't be the case in any professional framework. It's almost as if I could surprise you by saying that I can point you to dozens of frameworks and their documentations.
About performance:
According to a Google study, 53% of web users tenders to leave a site that takes longer than 3 seconds to load. Most sites take about 15 seconds to load.
First of all, the 53% are from a study on mobile traffic on landing-pages. Secondly, I don't know where the 15 seconds in the second sentence come from, but not from the think with google study you seem to quote from. But more importantly, this has little to do with laravel's performance. See when you want to make the point that website speed is everything (which makes sense for certain projects), then laravel simply isn't the answer. Laravel is a lot, but it is neither fast out of the box nor easy to optimize in comparison with other options.
About security
I am speechless regarding this paragraph. Security is a wide field and pointing out that laravel auto-generates the authentication flow says absolutely nothing about the framework's security in general nor it's structural design that helps navigate security or prevents exposing certain vulnerabilities. The only thing this paragraph makes clear is that I highly suggest to cooperate with a specialist before handing off a project that handles sensitive data.
Eloquent
Another paragraph full of misinformation: the way you describe what a model is makes it sound like the concept of MVC is a laravel-only design pattern. It is not!
You can easily enhance the performance of any business application using Models in Laravel
What? I can't even... No. Just no.
It is the only PHP framework that provides an easy way of building and customizing these models by using the Eloquent ORM.
This is so misleading that it's hard to imagine this is not intentional. Yes, laravel is (probably, as there isn't a technical reason for it) the only framework using the Eloquent ORM. But other frameworks do use ORMs and some of them even in a way more convenient way.
About blade
Okay, so blade is a (as in one of many) template engines. And laravel - like many others, but unlike some - ships with a template engine out-of-the-box rather than a developer having to decide on one (or the absence thereof). The rest of this paragraph seems to hammer down on the fact that OP is under the impression that blade is the only template engine ever written.
The conclusion
In this post, we have been exposed to some of the facts that qualify Laravel as the 1# backend Framework
We have not. This could have been an article of why you like working with laravel and how easy it was to get into it. Maybe how your transition to working with a professional and established framework like laravel has improved your work and your progress. Instead, you opted to misinform your fellow learners and beginners by pretending to offer some valid keypoints and some guidance on how and why to chose your favorite framework while filling their receptive and hungry brains with nothing but inaccuracy at it's best and utter nonsense at it worst.
I apologize for these words, but feel obligated to protect beginners from this potentially harmful gibberish.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really don't know what inspired this article, but I will have to try to keep my response as professional as possible, given how I feel about it.
Ignoring the click-baity title, the content itself is borderline propaganda. And I say that as someone who has a lot of respect for the technology in question and even regard it as one of the best frameworks myself.
As much as I wish that was true, this is simply wrong. PHP has dominated backend-development for decades but has lost popularity in recent years, despite very magnificent improvements.
This type of language is referred to as "lost speaker". If you were to ask "by whom is it regarded as the best PHP framework", you would quickly figure out that nobody is willing to say that. The reason for this is that experienced developers would hesitate to say something like "x is the best framework" as it always depends on the use-case. In my experience, whenever you hear someone say "x is the best framework" it usually means "x is the only framework I am comfortable working with".
For the reader: OP is likely referring to a particular benchmarking website phpbenchmaks. As of the time of writing this, the website lists a total of 7 PHP frameworks. So saying that it ranked 7th is very misleading as it distorts the fact that laravel ranks last in this particular benchmark comparison. It should be noted that there are countless different ways to benchmark performance and that there is only so much any benchmark test reveals about real-world performance, but this would be a topic within itself.
As compared to which framework? While proprietary frameworks exist, they are so rare that saying that all frameworks are open source and free is closer to the truth.
Again, which framework doesn't have elaborate documentation? Don't get me wrong, laravel has an exceptionally beautiful and nice to navigate documentation, but the way this is described makes it sound as this wouldn't be the case in any professional framework. It's almost as if I could surprise you by saying that I can point you to dozens of frameworks and their documentations.
About performance:
First of all, the 53% are from a study on mobile traffic on landing-pages. Secondly, I don't know where the 15 seconds in the second sentence come from, but not from the think with google study you seem to quote from. But more importantly, this has little to do with laravel's performance. See when you want to make the point that website speed is everything (which makes sense for certain projects), then laravel simply isn't the answer. Laravel is a lot, but it is neither fast out of the box nor easy to optimize in comparison with other options.
About security
I am speechless regarding this paragraph. Security is a wide field and pointing out that laravel auto-generates the authentication flow says absolutely nothing about the framework's security in general nor it's structural design that helps navigate security or prevents exposing certain vulnerabilities. The only thing this paragraph makes clear is that I highly suggest to cooperate with a specialist before handing off a project that handles sensitive data.
Eloquent
Another paragraph full of misinformation: the way you describe what a model is makes it sound like the concept of MVC is a laravel-only design pattern. It is not!
What? I can't even... No. Just no.
This is so misleading that it's hard to imagine this is not intentional. Yes, laravel is (probably, as there isn't a technical reason for it) the only framework using the Eloquent ORM. But other frameworks do use ORMs and some of them even in a way more convenient way.
About blade
Okay, so blade is a (as in one of many) template engines. And laravel - like many others, but unlike some - ships with a template engine out-of-the-box rather than a developer having to decide on one (or the absence thereof). The rest of this paragraph seems to hammer down on the fact that OP is under the impression that blade is the only template engine ever written.
The conclusion
We have not. This could have been an article of why you like working with laravel and how easy it was to get into it. Maybe how your transition to working with a professional and established framework like laravel has improved your work and your progress. Instead, you opted to misinform your fellow learners and beginners by pretending to offer some valid keypoints and some guidance on how and why to chose your favorite framework while filling their receptive and hungry brains with nothing but inaccuracy at it's best and utter nonsense at it worst.
I apologize for these words, but feel obligated to protect beginners from this potentially harmful gibberish.