well that's just not good enough, u should be reimplementing ur backend every few months in the latest and greatest and migrating your database back and forth between MongoDB, PostgreSQL and the latest whatever.
do you use blade or a FE frame work? for the past 18 months or so I've been using Laravel for my API server and Angular as my FE. i quite enjoy this setup but in the back of my mind i wonder if i should just stick to laravel for both
I want to start I have done some raw php at school, which laravel stack should I use as a somewhat beginner in web development? Also, does laravel fix full page refresh? Also I've only use a little Javascript for front end but I hate it
@@hungry_khid1007 you'd better start without starter kit so you won't get confused in the beginning. There are some tutorials on RUclips. You're welcome.
@@hungry_khid1007 I think the stack that you use depends on what you want to achieve. We use Laravel, with either Inertia+Vue for the more bespoke User front-end, or use Filament PHP for the admin side of the apps I work on. I would recommend checking out Filament PHP, since you can code entirely in PHP (it uses Laravel Livewire under the hood, which I am fairly basically skilled in). Bear in mind, filament PHP is more for building apps, if you want to build a really beautiful interactive website I don't think you can do it without Javascript (not in a meaningful way). Both of these frontends avoid full page refresh most of the time.
@@hungry_khid1007 you should search on google for laravel bootcamp, and try it. this will answer almost all your question. About full page refresh, you also will find the a answer, however you should try with js + xhr / fetch / axios or with a solution like htmx. ;)
Laravel's focussed efforts to simplify things for the dev has really made it shine. In a way, it has made php and full-stack development cool and enjoyable again. Its a welcome relief from the stress and fatigue of keeping up with constantly changing JS frameworks.
Laravel is on a different level, it's already incredible before even more so today. Everything is just easy with Laravel when it comes to web development.
@@Ali-lm7uw It's a JavaScript library + adapter that allows you to connect a back end framework to a page built with a front end framework. Instead of your back end being an API project that is completely separate from your front end, they're a bit more connected. Normally, in a server side rendered back end application, a controller will return a HTML template file that you can fill in with values from your app. Inertia lets you return a template written with your JS framework of choice, and you can pass values from your app to the component as props.
PHP Developer for over a decade, almost a year in Laravel, and it is really good. Maybe I don't know about other great tools but this one is sufficient, at least for now.
I am the one who keeps trying different things all the time. My advice is to stick to it. It has been 5 years where I tinker with much stuff, but when it comes to doing reliable things, I blindly choose Laravel.
Fantastic docs, smooth framework and Jeffrey Way. I think the fact that Jeffrey Way of Laracasts is one of the best technical teachers on the internet has a huge role to play in making Laravel what it is.
For Web development, Laravel is always my favourite ❤❤. Simple MVC, Clean very fast. Within minutes, your product is accessible on the Web. The Docs cover every aspect of the framework, with bootcamps, great details and we'll structured. Grateful to the Laravel Team & Community ❤❤
What people like about PHP (and Ruby for that matter) is that Laravel and Symfony are pretty much the defacto frameworks and it’s an easy choice. Composer is the goto package manager. That’s it. With Ruby it’s RoR. With JavaScript, it’s fucking annoying and exhausting all the frameworks du jour. Then you wake up tomorrow and there’s another framework that is trying to supersede the previous ones. Same with the package manager. Which one is it? npm? yarn? pnpm? Make up your fucking mind people! You wanna get people confused and reluctant to your software then give them too many choices and never agree or reach consensus . In fact, fragment your ecosystem amongst frameworks and within your frameworks.
I have worked with many technologies and so far i can say that laravel gives me the highest productivity. It is also very nice that the ecosystem is not so fragmented making dependency handling easy
Laravel is my first framework and my gateway to Software Industry. It helped me, became my bread and butter of my life. Helped me switched to Software from my previous profession. Documentation of Laravel is just awesome and love so much that i don't like other documentation xD . Addicted to its migration feature, seeder. Framework is so flexible to all needs. With upcoming php 9 and 10 which boost php power as whole will be game changer.
The best part about Laravel is that sometimes you don't need a big server, so you host on shared hosting (most of these services only support PHP and are usually cheap). And if you need to scale, it's relatively easier.
I’m a React/NextJS developer and loving its capabilities. In the past worked with PHP more than a decade and used Laravel briefly (never liked PHP syntax and workflow due to classes and namespaces). But I want to congratulate Laravel team because they used similar hype of JS frameworks with fancy micro service titles, features and branding to revive PHP popularity again. Apparently React’s full-stack approach gave them an opportunity to shine and I must say they do a great job spreading the word.
I'm currently into web development, but my heart always pulls me back to Laravel. I'm diligently studying and would gladly welcome any advice, roadmaps, or courses, as I'm very new to it. Please wish me success!
I own a marketing company, I run in WordPress but I've been refreshing my Laravel skills for two weeks because I think I'm moving all my sites to Laravel in the near future.
The funny thing is that if more companies started using Laravel, they wouldn't need to hire as many people to manage their apps. It would just work lol
Hi, Laravel has a good Docs, however Symfony has better. And one thing that almost everyone dont pay attention or dont care, is the fact that laravel under the hood use some components / libs of Symfony. Symfony never was only framework, It has stand alone components and since Symfony version 5 is more like Vuejs, a progressive framework, where in symfony you start only as a router, if you only want as web API, you choose your own ORM or even use it without it. Add a view engine, if you are creating traditional web app, like twig or choose other or go with plain php, your choice. Ssymfony is not bloated when you start, like laravel, symfony start small. And to finish, symfony take advantage on latest feature of PHP when they are available, for example PHP attributes, released on php 8.0, symfony in next version was already use it in the routing system where laravel only now since this month it start take advantage with few attributes, only after 4 years. LOL. 😱
@@ivanjelenic5627 Lol. Recommend you to read the docs of symfony. For me , Laravel only has this 2 positive points better than symfony; - Great integration with modern frontend solutions ( even with some costs over time) - it is thanks to laracast with great and free content, in my opinion, that makes a big diff and of course nowadays exist a lot of content on youtube and on learning plataforms than symfony ( which even has something similar to laracast) With symfony as a framework ( because exist also symfony components which some for example laravel use), give you choices, install it as full framework with everything you already setup and ready to create websites or web apps or start small and simple as router and install only the packages / components you think you need. And your are always using the latest features of PHP. Just see how simple and clean the routing system of symfony is. With laravel, you only have one place and a way to define routes. Be prepare to organize your routes, even routes as resources or groups, always will exist a lot of definitions and you wll have to find a way to organize and keep it clean. This is not a exclusive problem of laravel, this can happen in another php framework like cakePHP, phaconPHP, CI4 (however they have other alternative way to define routes) and even in other framework on js universe backend or frontend. Another problem with laravel: is bloated , even that they start to trim it, However in the wrong way, They should look at what symfony and node js version of laravel, call adonisJS did. Start small and simple. What i mean being bloated ? for example if you are building a Web api, why you need a template engine installed, why you need a package for session or cookies, why you need things related to frontend. The official or not official packages should only be install when you need it. This is a problem on ecosystem of some frameworks on PHP, JS, etc,
Symfony's documentation was the best a while back but Laravel really raised the bar. Symfony has been catching up in recent years but still has some work do to, and I say this as a developer who would pick Symfony over Laravel any day of the week.
2:20 Not to mention if its an SPA like app you want, Laravel has you covered with Interntia for Vue or React front ends, or Livewire's new SPA mode (which while not strictly an actual SPA operates like one by just switching out the parts of the DOM that change instead of a full reload).
Symfony's documentation won't give you a production code; it will only give you a glue of the concept and API they expose. Very unpractical, with a lot of unnecessarily complicated boilerplate (and source) code and YAML configurations. That's what Symfony is all about. It is seriously overrated among guys who use it and they can't even give objective arguments why. They spent that insanely huge amount of time learning it they don't want to learn something else. They will say that Laravel has facades or an Active Record ORM and that's ruining the world so we need to continue using Symfony... Give yourself a favor and leave it alone.
Great coverage! I’m totally all for batteries-included, convention over configuration. It’s enough already on one’s plate to ship accessible, SEO friendly, responsive apps with decent UX, error handling, appropriate schema designs, integration with 3rd party services, metrics, testing, deployment… That said, I come from using Phoenix (Elixir) which also has excellent docs and conventions, but doesn’t promote a full-suite of great available utilities
Once I tried inertiaJS I couldn’t go back. The PHP back end is really elegant, and the front-backend integration is so smooth. I like coding in JavaScript when the project is new, but when a project sprawls out in size it can get really frustrating and ugly to look at. The PHP code when done properly just seems to keep everything bite size and simple to understand and work on. Even when the project gets really large, the code is correctly compartmented into a file for its relevant concern. It just feels cleaner.
i love your videos,.... i saved some of your videos in media wallet so i could revisit them for future references. please continue to make these typa content
I don't wish for Nextjs to go full throttle on opinionating stuff, but I wish for more stacks to popup for easier project kick-start. Tho, very few people need to kick-start lots of project in a short period of time.
People confuse paths. Enterprise developer; full stack midsize; freelance developer; startup developer All have common denominators but are very different. Influencers like being controversial for views and confuse newbies. Rough times.
@@TravisMedia I wasn’t strictly talking about this video/you even tho you bashed .net because of Microsoft even though the documentation is comprehensive. But my point was these are all tools it’s not one or the other. Saying a shovel is better than an excavator because it’s ergonomic is not only wrong but short sited. I like your videos. I just wanted to share that with the channel.
Its because laravel is complete. From the routings, migrations, ORM, queueing, etc.. It all comes during installation unlike in any other framework like Nodejs express where you have to install all the packages you need.
If you want to play with cool stuff, go with the JS ecosystem. For reliable, real-world tasks that save time, choose Laravel and PHP. In all cases, the tools should fit the purpose you need. And for me , Laravel is all I need for my life.
Ruby on Rails, the framework that set the standard for MVC frameworks since its introduction in 2005, has been widely influential. If a new developer were to ask whether to pursue PHP Laravel or another path, I would advise them to consider JavaScript technologies like NodeJS, React, and Next.js, along with SQL and NoSQL databases such as MongoDB. This recommendation is based on the earning potential, as developers specializing in these technologies tend to have higher salaries compared to those focusing on PHP-based development.
Also, because JavaScript as a language and skillset is easily transferable to other platforms such as building desktop based applications with Electron and mobile applications with React Native.
I would only consider focusing on JavaScript taking into account the potential to also build mobile apps via React Native and just by sharing components with a web based React application. However, if I’m a solo developer trying to build product, I would just use Laravel or Rails, just because of how quickly you can ship.
Big fan of both rails and laravel. One thing I’d say is the “quietness” of the rails community is that it has some benefits. Rails devs have just got their heads down, doing stuff. Once you enter the ecosystem you begin to realise the sheer number of products still built with it. The community itself is incredibly friendly, filled to the brim with knowledgeable people keen to share that knowledge in a positive way. It’s probably the nicest dev community I’ve come across. Even moreso than Laravel, which is also generally very friendly. The thing rails could really do with, is their version of laracasts. Gorails exists but it doesn’t have quite the same energy or coverage
As a long-time Ruby developer, I disagree on some minor points 😉, but I'm fully on board with making pragmatic choices that don't depend on the flavour of the month.
I started using Laravel (as a professional) a few months ago. For doing the same thing, you often write less lines of code than with Symfony. But I think Symfony has a better documentation and more flexibility.
no matter how much you hate js you cant completely ditch js and you dont need fancy frameworks to get job done with vanilla js jamstack you can build any application
2:00 wait until people find out that you can use React as the view layer of Laravel (with components, interaction, spa navigation, and everything else), and you don't need to wire up several packages together just to have basic authentication, caching, queueing, mailing, and other stuff that comes out of the box in Laravel.
If you are thinking about Inertia, I'm doing a project with it but I am now thinking about replacing it by just doing classical SPA and Laravel for the Backend I think it's just easier. If you are ok with basically reloading the page on every state update Inertia is ok. But if you have a mix of Ajax calls and page reloads it's hard to master.
@@blubblurb you're not supposed to be getting page reloads when the state changes, but only when navigation occurs. Are you sure you're not using some form of `Inertia.reload()`?
@@rodrigorios78 Oh I do router.reload() on purpose, because I do some Ajax calls and the same page needs to reflect the change of that data. But it would be easier if I could just do the ajax request and change the state after the call using JS. But that's not how it works with inertia. The reload is not really visible for the user, so I don't mind it too much. Simple example, delete an item of the list. Instead of removing that item from the state after the ajax call you would do router.reload() or instead of ajax + router.reload you would do router.visit in one call. But anyway you would usually return the full new state in that call.
SvelteKit DX is just so good. Also, once the client side router loads, its page navigation performance is amazing compared to loading a new page each time.
@@reze_dev it’s still “new” compared to other mainstream frameworks. Svelte 5 is going to have even better performance. I’ve been running my own comparisons of Svelte vs Astro vs Qwik. Yes, the other two have a marginal first time load performance advantage, but after that you’re only loading a few KB at a time. Amazing for slower connections
I hate people when they overhype something that isn't worth it. Laravel just does the job, why do people hate it? Some people literally worship JavaScript and other techs like Rust, Ruby, etc..
It's not like many people will use all its features. NextJS, SvelteKit are way simpler and don't throw at me unnecessary features or a complex architecture Also PHP is a joke in static typing when compared with TypeScript
What about a social media chatting app, where users can have star progress increase depending on how long they stay on the app. From Novice to legend star progress. 6-7 star progress in between novice and legend. just a simple interface like WhatsApp, users create their group themselves to chat with friends and family. A group where user can boost their star progress also by engaging in ai generated games in different fields. e.g sport, programming etc. leader board page with points earned.
How much PHP do i need to know before learning Laravel? Installing, setting up stuff or deploying to a Linux server is what i like the most 😊 I'm finishing the OOP section of PHP & MySQL by Jon ducket. Do i need to complete the book like going into database driven web sites? How much SQL should i know? How much OOP PHP should I know? I've already build some responsive websites with html css and bootstrap.
leran basic sql queries upadte delete select and stuff learn first leanr php and get really good with php oop interfaces and stuff them come to laravel php oop is the key to mastering laravel
i noticed personally, the use of ctrl-shift-f5 has increased for me since the raise of SPAs. which page refresh is worse: the actual needed one or the one i am forced to do bc the FE tries to be clever, fails and gets stuck somewhere??? the latter one is the worse UX as it completely undoes all of the pretended benefits. just fetch the damn page. i can wait.
Sorry I got to the part where you said Laravel didn't have fan bois and I nearly spit out my red bull. That community was the biggest fan community I ever experienced, Taylor "Lambo" Otwell could do no wrong and if you said anything bad about him you were immediately attacked. Super toxic a few years ago.
but that's not a Laravel thing. that's an every language / framework thing. just think pythonistas. those fan boys even have a name. which for some reason just makes me think of coffee
PHP has been my primary language since 1998. I don't generally use Laravel. Not because I wouldn't use Laravel, because my software is so specific and the opinions do get in the way for my requirements. I build my own light-weight framework with many of the same packages. But, guess where I go first when I want to see how someone else has solved a problem in a elegant manner ...the Laravel docs. If I wanted to spin up a typical SaaS, I'd go straight to Laravel. All these languages are just a tool. Pick the one(s) for you. I still do a ton of JS/React, etc.
Because nothing can replace js, and it freedom to build your customize app tailored to your needs, lavaral is just too one sided, which is a risk for companies
Laravel docs is great. However the article submenu is not sticky and I must always scroll up to see it again, which is annoying. 😒 I solved it by creating a custom stylesheet which makes the menu stick to the right side of the page. Much better experience! 😏
Give me some suggestions.Currently i am learning MERN stack and have done html/css/js/react and now on next js. Should i have to learn Laravel or go for node.js like MERN stack is so saturated now
While Laravel is fun, and for hobbiest. To be honest, the ecosystem, community ,libraries around React, Angular, Vue, NextJS are much much bigger. The prospect for Laravel in Enterprise apps is tiny
if you need simple things that's only be enough for small projects (like email as you said) yeah go use laravel, but it's never gonna be enough for big projects and if your program become popular your gonna face big issues
i use it on some fairly busy sites (several thousand visitors at peak times). no issues. granted its not millions of visitors but its a decent amout of users......
No, you must be out of your mind to say thats first time laravel user like it in 2024, because i dont. Its full of abstraction. Its not slow or bad and it has some level of community but i genuinely dont think you should start laravel in 2024 just because of the syntax and weird orm like Eloquent, personally i prefer something like sqlc or prisma. And the server setup is a madness compared to js. You really need to dig up a lot of deps from years ago
The job market has definitely seen a downturn, and Laravel seems to be struggling to maintain its relevance. It appears that they’re trying to revive interest by leveraging social media influencers for promotion. While Laravel is a decent framework, it’s extremely opinionated and built on top of PHP, which has a mixed reputation. Over the years, it has improved by incorporating elements from languages like C#, Java, and JavaScript. Personally, I enjoyed using Laravel up until version 7. However, the frequent major version releases one every year have become a significant burden, as they require constant updates to keep your applications up to date. Lack of built-in generics in PHP is one of the things that makes type-hinting in PHP a nightmare. They're still one step behind the big players like Java and C# when we talk about enterprise application.
@@yashuabaryosef4413 great nuanced answer! For large scale, it really does not hold up as well as the likes of Java/modern .net and for smaller, more agile teams…honestly I’d just go with rails now. You don’t have the same development pace in Laravel and despite rails’ reputation, it’s much less restrictive than Laravel and holds together better when you need to do novel things with the framework. If you’re just serving an API, I’d still probably go with rails, I prefer active record to eloquent, rails routing is immensely good and rails is also a little faster than Laravel.
Laravel v5.8 + queue jobs features from the v8 was the best version of Laravel.. basically everything else is just hype inspired from non-stable JS world
I am learning laravel. Its very good, But using it as api for backend it gives less help. like no starter kit for api. there is breeze api but need to edit a lot to work with it for api. other problem i encountered is if i am using it as an api when i sent mail for reset password or mail verification i need to edit the code in appservice provider for appending frontend url. or it will send the link with backend url. I think laravel framwork is focusing on full stack using inertia . it gives less support in api development.
Never like Ruby either. Used Laravel off on and for years but haven't used it for about 5. Have to disagree about .Net. It may not have all the docs in one place but the support and training for it are everywhere.
I enjoyed the video, but the idea that "criticisms of PHP are unfounded" is just not true. Maybe dev's feedback should be heard and not dismissed as "hate". The same goes for JavaScript, PHP, NextJS, or any other language/technology. It's always easier to say "hater", than understand where the criticism comes from, because people's intentions are not bad most of the time, they're just expressing they're experience when using a language/technology.
It is unfounded most of the time because people compare it to the wrong things, and for being used for the wrong purposes. And hate? Who said anything about hate? It's just a language
Php developer here for 10 years and laravel for 7 years. It get's the job done, smoothly and beautifully. That's what I can say.
Absolutely!
well that's just not good enough, u should be reimplementing ur backend every few months in the latest and greatest and migrating your database back and forth between MongoDB, PostgreSQL and the latest whatever.
@@illegalsmirf Hehe! Yep! Exactly!
@@illegalsmirf i see what you did there lol!
do you use blade or a FE frame work? for the past 18 months or so I've been using Laravel for my API server and Angular as my FE. i quite enjoy this setup but in the back of my mind i wonder if i should just stick to laravel for both
Laravel Developer here. The #4 - Documentation is a great point, they have really nailed it!
I want to start I have done some raw php at school, which laravel stack should I use as a somewhat beginner in web development? Also, does laravel fix full page refresh? Also I've only use a little Javascript for front end but I hate it
@@hungry_khid1007 you'd better start without starter kit so you won't get confused in the beginning. There are some tutorials on RUclips. You're welcome.
@@hungry_khid1007 I think the stack that you use depends on what you want to achieve. We use Laravel, with either Inertia+Vue for the more bespoke User front-end, or use Filament PHP for the admin side of the apps I work on. I would recommend checking out Filament PHP, since you can code entirely in PHP (it uses Laravel Livewire under the hood, which I am fairly basically skilled in). Bear in mind, filament PHP is more for building apps, if you want to build a really beautiful interactive website I don't think you can do it without Javascript (not in a meaningful way).
Both of these frontends avoid full page refresh most of the time.
Rehnede Bhai, Desi Channels Pe Ja @@hungry_khid1007
@@hungry_khid1007 you should search on google for laravel bootcamp, and try it. this will answer almost all your question.
About full page refresh, you also will find the a answer, however you should try with js + xhr / fetch / axios or with a solution like htmx. ;)
Laravel's focussed efforts to simplify things for the dev has really made it shine. In a way, it has made php and full-stack development cool and enjoyable again. Its a welcome relief from the stress and fatigue of keeping up with constantly changing JS frameworks.
Nicely said
After 14 years as a web developer I finally decided to create something with laravel last month and basically that's the only thing I'm doing since
Try symfony next ;)
@@choanlpoto I tried Symphony after I tried Laravel, it is good. but there is a lot of tinkering to get the template you want
tried symfony as a musician, S&M was good but the framework is garbage wasting my time
How is it going?
@@choanlpoto .. Laravel is built on top of Symfony.
when you embrace laravel, programming becomes fun again
For me it’s react
@@tuananhdo1870React and Fun?
True
Laravel is on a different level, it's already incredible before even more so today. Everything is just easy with Laravel when it comes to web development.
Laravel + Inertia + {Vue,React,Svelte} is an unbeatable stack
I literally tried it yesterday, never looking at any other framework EVER
true
but is it highly required nowdays?
there is low percent of such stacks in market unfortunately
What is inertia?
@@Ali-lm7uw It's a JavaScript library + adapter that allows you to connect a back end framework to a page built with a front end framework. Instead of your back end being an API project that is completely separate from your front end, they're a bit more connected. Normally, in a server side rendered back end application, a controller will return a HTML template file that you can fill in with values from your app. Inertia lets you return a template written with your JS framework of choice, and you can pass values from your app to the component as props.
I love Laravel + Inertia
Laravel drives our IoT business very well. It's a joy to develop with Laravel!
I am a Laravel developer. when I started learning web development Laravel documentation helped me not give up on it.
PHP Developer for over a decade, almost a year in Laravel, and it is really good. Maybe I don't know about other great tools but this one is sufficient, at least for now.
I am the one who keeps trying different things all the time. My advice is to stick to it. It has been 5 years where I tinker with much stuff, but when it comes to doing reliable things, I blindly choose Laravel.
Fantastic docs, smooth framework and Jeffrey Way. I think the fact that Jeffrey Way of Laracasts is one of the best technical teachers on the internet has a huge role to play in making Laravel what it is.
For Web development, Laravel is always my favourite ❤❤. Simple MVC, Clean very fast. Within minutes, your product is accessible on the Web.
The Docs cover every aspect of the framework, with bootcamps, great details and we'll structured.
Grateful to the Laravel Team & Community ❤❤
Laravel is a game changer. Those who don't use it are ignorant of its power and those who use it are constantly mind blown. :)
What people like about PHP (and Ruby for that matter) is that Laravel and Symfony are pretty much the defacto frameworks and it’s an easy choice. Composer is the goto package manager. That’s it. With Ruby it’s RoR.
With JavaScript, it’s fucking annoying and exhausting all the frameworks du jour. Then you wake up tomorrow and there’s another framework that is trying to supersede the previous ones. Same with the package manager. Which one is it? npm? yarn? pnpm? Make up your fucking mind people!
You wanna get people confused and reluctant to your software then give them too many choices and never agree or reach consensus .
In fact, fragment your ecosystem amongst frameworks and within your frameworks.
framework of a framework of another framework on top of another framework.
I think you never heard abt package-lock.json
All trying to replicate a clunkier, more fragmented version of something Laravel or rails was doing in 2015
So true!
Go !
I have worked with many technologies and so far i can say that laravel gives me the highest productivity. It is also very nice that the ecosystem is not so fragmented making dependency handling easy
Do u use live wire or inertia with a vue/rect? I'm a beginner and I want to know which to use
@@hungry_khid1007x2
Laravel is my first framework and my gateway to Software Industry. It helped me, became my bread and butter of my life. Helped me switched to Software from my previous profession. Documentation of Laravel is just awesome and love so much that i don't like other documentation xD . Addicted to its migration feature, seeder. Framework is so flexible to all needs.
With upcoming php 9 and 10 which boost php power as whole will be game changer.
The best part about Laravel is that sometimes you don't need a big server, so you host on shared hosting (most of these services only support PHP and are usually cheap). And if you need to scale, it's relatively easier.
I've been a Laravel fan for years, but this new funding and Laravel Cloud? Game changer! 💥
I’m a React/NextJS developer and loving its capabilities. In the past worked with PHP more than a decade and used Laravel briefly (never liked PHP syntax and workflow due to classes and namespaces). But I want to congratulate Laravel team because they used similar hype of JS frameworks with fancy micro service titles, features and branding to revive PHP popularity again. Apparently React’s full-stack approach gave them an opportunity to shine and I must say they do a great job spreading the word.
Yikes
I'm currently into web development, but my heart always pulls me back to Laravel. I'm diligently studying and would gladly welcome any advice, roadmaps, or courses, as I'm very new to it. Please wish me success!
20 years in PHP 100% love this video!!
I love all the positivity from Laravel users in the comments, has me excited to give it a try myself!
Laravel has everything you ever need to build real world applications and it get better and better every week.
Great insight, I am using Laravel since 2022 and it is a great tool :)
I own a marketing company, I run in WordPress but I've been refreshing my Laravel skills for two weeks because I think I'm moving all my sites to Laravel in the near future.
Laravel, Inertia, Vue and Tailwind, the best stack on planet❤
Those 2 memes in the beginning had me rolling
Laravel is fine. Most non-JS frameworks are. Biggest con is the job opportunities.
That’s true
Depends on country. Things are very very different outside the USA. UK is very much a PHP dominated market
True for the US. I’m from the UK, and the job opportunities are very good for PHP and Laravel.
The funny thing is that if more companies started using Laravel, they wouldn't need to hire as many people to manage their apps. It would just work lol
that documenation part is spot on,reading laravel docs was smooth and straightforward,unlike .net asp,just find the right docs was a headache
was a WP dev for over 10 years. Laravel is something im giving serious consideration to move over too now especially with the latest fallout.
Hi, Laravel has a good Docs, however Symfony has better.
And one thing that almost everyone dont pay attention or dont care, is the fact that laravel under the hood use some components / libs of Symfony.
Symfony never was only framework, It has stand alone components and since Symfony version 5 is more like Vuejs, a progressive framework, where in symfony you start only as a router, if you only want as web API, you choose your own ORM or even use it without it. Add a view engine, if you are creating traditional web app, like twig or choose other or go with plain php, your choice.
Ssymfony is not bloated when you start, like laravel, symfony start small.
And to finish, symfony take advantage on latest feature of PHP when they are available, for example PHP attributes, released on php 8.0, symfony in next version was already use it in the routing system where laravel only now since this month it start take advantage with few attributes, only after 4 years. LOL. 😱
No. Laravel docs are much better. And Laravel is simply better and simpler than Symfony for a vast majority of people.
@@ivanjelenic5627 Lol. Recommend you to read the docs of symfony.
For me , Laravel only has this 2 positive points better than symfony;
- Great integration with modern frontend solutions ( even with some costs over time)
- it is thanks to laracast with great and free content, in my opinion, that makes a big diff and of course nowadays exist a lot of content on youtube and on learning plataforms than symfony ( which even has something similar to laracast)
With symfony as a framework ( because exist also symfony components which some for example laravel use), give you choices, install it as full framework with everything you already setup and ready to create websites or web apps or start small and simple as router and install only the packages / components you think you need. And your are always using the latest features of PHP. Just see how simple and clean the routing system of symfony is.
With laravel, you only have one place and a way to define routes. Be prepare to organize your routes, even routes as resources or groups, always will exist a lot of definitions and you wll have to find a way to organize and keep it clean. This is not a exclusive problem of laravel, this can happen in another php framework like cakePHP, phaconPHP, CI4 (however they have other alternative way to define routes) and even in other framework on js universe backend or frontend.
Another problem with laravel: is bloated , even that they start to trim it, However in the wrong way, They should look at what symfony and node js version of laravel, call adonisJS did. Start small and simple.
What i mean being bloated ? for example if you are building a Web api, why you need a template engine installed, why you need a package for session or cookies, why you need things related to frontend.
The official or not official packages should only be install when you need it.
This is a problem on ecosystem of some frameworks on PHP, JS, etc,
Symfony's documentation was the best a while back but Laravel really raised the bar. Symfony has been catching up in recent years but still has some work do to, and I say this as a developer who would pick Symfony over Laravel any day of the week.
2:20 Not to mention if its an SPA like app you want, Laravel has you covered with Interntia for Vue or React front ends, or Livewire's new SPA mode (which while not strictly an actual SPA operates like one by just switching out the parts of the DOM that change instead of a full reload).
Laravel has the best documentation. ❤
Have you seen Symfonys documentation? One of the best I've seen.
And also has a big slack community.
ART
I have honestly never used Symfony. I’ll check it out. Thanks for mentioning.
Symfony is seriously underrated!!!! Best framework in my opinion. The marketing team there seriously need to up their gane.
I used Symfony in the old days with propel ORM. Nowadays, I used laravel though.
Symfony's documentation won't give you a production code; it will only give you a glue of the concept and API they expose. Very unpractical, with a lot of unnecessarily complicated boilerplate (and source) code and YAML configurations. That's what Symfony is all about. It is seriously overrated among guys who use it and they can't even give objective arguments why. They spent that insanely huge amount of time learning it they don't want to learn something else. They will say that Laravel has facades or an Active Record ORM and that's ruining the world so we need to continue using Symfony... Give yourself a favor and leave it alone.
Great coverage! I’m totally all for batteries-included, convention over configuration. It’s enough already on one’s plate to ship accessible, SEO friendly, responsive apps with decent UX, error handling, appropriate schema designs, integration with 3rd party services, metrics, testing, deployment…
That said, I come from using Phoenix (Elixir) which also has excellent docs and conventions, but doesn’t promote a full-suite of great available utilities
Once I tried inertiaJS I couldn’t go back. The PHP back end is really elegant, and the front-backend integration is so smooth. I like coding in JavaScript when the project is new, but when a project sprawls out in size it can get really frustrating and ugly to look at. The PHP code when done properly just seems to keep everything bite size and simple to understand and work on. Even when the project gets really large, the code is correctly compartmented into a file for its relevant concern. It just feels cleaner.
i love your videos,.... i saved some of your videos in media wallet so i could revisit them for future references. please continue to make these typa content
I don't wish for Nextjs to go full throttle on opinionating stuff, but I wish for more stacks to popup for easier project kick-start.
Tho, very few people need to kick-start lots of project in a short period of time.
People confuse paths. Enterprise developer; full stack midsize; freelance developer; startup developer All have common denominators but are very different. Influencers like being controversial for views and confuse newbies. Rough times.
You overthought this video
@@TravisMedia I wasn’t strictly talking about this video/you even tho you bashed .net because of Microsoft even though the documentation is comprehensive. But my point was these are all tools it’s not one or the other. Saying a shovel is better than an excavator because it’s ergonomic is not only wrong but short sited.
I like your videos. I just wanted to share that with the channel.
@@TravisMediayea he did
My response is gone lol 😂
to be fair I don't he was talking about you. i think he meant many of those influencers who dump on laravel or php etc do so just for the clicks
Its because laravel is complete. From the routings, migrations, ORM, queueing, etc..
It all comes during installation unlike in any other framework like Nodejs express where you have to install all the packages you need.
If you want to play with cool stuff, go with the JS ecosystem. For reliable, real-world tasks that save time, choose Laravel and PHP. In all cases, the tools should fit the purpose you need. And for me , Laravel is all I need for my life.
I also need Python and plain JS. Just exaggeration.
Ruby on Rails, the framework that set the standard for MVC frameworks since its introduction in 2005, has been widely influential. If a new developer were to ask whether to pursue PHP Laravel or another path, I would advise them to consider JavaScript technologies like NodeJS, React, and Next.js, along with SQL and NoSQL databases such as MongoDB. This recommendation is based on the earning potential, as developers specializing in these technologies tend to have higher salaries compared to those focusing on PHP-based development.
Also, because JavaScript as a language and skillset is easily transferable to other platforms such as building desktop based applications with Electron and mobile applications with React Native.
looks like an ai generated response lol
@@losmandev looks like it but its honest and realistic, I share the same opinion
I would only consider focusing on JavaScript taking into account the potential to also build mobile apps via React Native and just by sharing components with a web based React application.
However, if I’m a solo developer trying to build product, I would just use Laravel or Rails, just because of how quickly you can ship.
Thank you Mr. GPT.
I'd add Laracasts to this list.
Laravel + Inertia + (Vue or React depends) + Tailwind + (Any tailwind UI Framework)
Big fan of both rails and laravel. One thing I’d say is the “quietness” of the rails community is that it has some benefits. Rails devs have just got their heads down, doing stuff. Once you enter the ecosystem you begin to realise the sheer number of products still built with it. The community itself is incredibly friendly, filled to the brim with knowledgeable people keen to share that knowledge in a positive way. It’s probably the nicest dev community I’ve come across. Even moreso than Laravel, which is also generally very friendly.
The thing rails could really do with, is their version of laracasts. Gorails exists but it doesn’t have quite the same energy or coverage
Thanks for sharing this
You people from USA act like symfony doesn’t even exist ! Insane when it’s more robust, fast and easy than laravel
@@choanlpoto 🤷
As a long-time Ruby developer, I disagree on some minor points 😉, but I'm fully on board with making pragmatic choices that don't depend on the flavour of the month.
I started using Laravel (as a professional) a few months ago. For doing the same thing, you often write less lines of code than with Symfony. But I think Symfony has a better documentation and more flexibility.
no matter how much you hate js you cant completely ditch js and you dont need fancy frameworks to get job done with vanilla js jamstack you can build any application
Laract here! Yes, it less painfull for making website with it.
Opinions make for fast development, when those opinions coincide with your requirements
2:00 wait until people find out that you can use React as the view layer of Laravel (with components, interaction, spa navigation, and everything else), and you don't need to wire up several packages together just to have basic authentication, caching, queueing, mailing, and other stuff that comes out of the box in Laravel.
Wire up several package is ok. Because you understand and can modify them
If you are thinking about Inertia, I'm doing a project with it but I am now thinking about replacing it by just doing classical SPA and Laravel for the Backend I think it's just easier. If you are ok with basically reloading the page on every state update Inertia is ok. But if you have a mix of Ajax calls and page reloads it's hard to master.
@@tuananhdo1870 I understand that some projects have specific needs, but Laravel allows you to modify stuff too, via the container.
@@blubblurb you're not supposed to be getting page reloads when the state changes, but only when navigation occurs. Are you sure you're not using some form of `Inertia.reload()`?
@@rodrigorios78 Oh I do router.reload() on purpose, because I do some Ajax calls and the same page needs to reflect the change of that data. But it would be easier if I could just do the ajax request and change the state after the call using JS. But that's not how it works with inertia. The reload is not really visible for the user, so I don't mind it too much.
Simple example, delete an item of the list. Instead of removing that item from the state after the ajax call you would do router.reload() or instead of ajax + router.reload you would do router.visit in one call. But anyway you would usually return the full new state in that call.
I used to love Laravel with Livewire, but i prefer Sveltekit
tell me about it
i love both
SvelteKit DX is just so good. Also, once the client side router loads, its page navigation performance is amazing compared to loading a new page each time.
@@charlesbcraig Yeah, I wonder why not so many big projects use Sveltekit.
@@reze_dev it’s still “new” compared to other mainstream frameworks. Svelte 5 is going to have even better performance. I’ve been running my own comparisons of Svelte vs Astro vs Qwik. Yes, the other two have a marginal first time load performance advantage, but after that you’re only loading a few KB at a time. Amazing for slower connections
Honeslty Django has it all and should be mentioned more.
I started with Django(It's still my favorite) and that's right - Django has it all. But Laravel's Documentation is so much good.
@@DevCyberOps and laravel’s great adoption for building frontend (full stack) projects makes me like it a bit more than django 😊
I hate people when they overhype something that isn't worth it. Laravel just does the job, why do people hate it? Some people literally worship JavaScript and other techs like Rust, Ruby, etc..
Momentum has a factor in tech trends.
I did PHP for many years, but I have new language interests now.
It's not like many people will use all its features. NextJS, SvelteKit are way simpler and don't throw at me unnecessary features or a complex architecture
Also PHP is a joke in static typing when compared with TypeScript
I also think the simple-page app phenomenon has also started to wear out its welcome.
I tend to switch frameworks pretty often so I don't get stagnant. Next is Laravel!
Anyone has any cool project ideas, drop a comment! 😄
shut up 😄
@@zahash1045 🤥 that's mean
What about a social media chatting app, where users can have star progress increase depending on how long they stay on the app. From Novice to legend star progress. 6-7 star progress in between novice and legend. just a simple interface like WhatsApp, users create their group themselves to chat with friends and family. A group where user can boost their star progress also by engaging in ai generated games in different fields. e.g sport, programming etc. leader board page with points earned.
i personally switched to golang it's easy elegant & fast + the standard lib is huge
How much PHP do i need to know before learning Laravel?
Installing, setting up stuff or deploying to a Linux server is what i like the most 😊
I'm finishing the OOP section of PHP & MySQL by Jon ducket. Do i need to complete the book like going into database driven web sites?
How much SQL should i know?
How much OOP PHP should I know?
I've already build some responsive websites with html css and bootstrap.
leran basic sql queries upadte delete select and stuff learn first leanr php and get really good with php oop interfaces and stuff them come to laravel php oop is the key to mastering laravel
Laravel developers are also everywhere!
True
i noticed personally, the use of ctrl-shift-f5 has increased for me since the raise of SPAs. which page refresh is worse: the actual needed one or the one i am forced to do bc the FE tries to be clever, fails and gets stuck somewhere??? the latter one is the worse UX as it completely undoes all of the pretended benefits. just fetch the damn page. i can wait.
Sorry I got to the part where you said Laravel didn't have fan bois and I nearly spit out my red bull. That community was the biggest fan community I ever experienced, Taylor "Lambo" Otwell could do no wrong and if you said anything bad about him you were immediately attacked. Super toxic a few years ago.
but that's not a Laravel thing. that's an every language / framework thing. just think pythonistas. those fan boys even have a name. which for some reason just makes me think of coffee
Would Larafellas work? 😉
Hahaha, pythonists even say that PHP developers code in index.php file these days!
As .Net developer and who has used Laravel (v7 to v10) for my side project its true the Laravel have way better documentation.
I like rails and nuxt
I love building web app in laravel
PHP has been my primary language since 1998. I don't generally use Laravel. Not because I wouldn't use Laravel, because my software is so specific and the opinions do get in the way for my requirements. I build my own light-weight framework with many of the same packages. But, guess where I go first when I want to see how someone else has solved a problem in a elegant manner ...the Laravel docs. If I wanted to spin up a typical SaaS, I'd go straight to Laravel. All these languages are just a tool. Pick the one(s) for you. I still do a ton of JS/React, etc.
I like laravel backend and react frontend, I don't even try to look at nextjs.
Why not Rails or Spring Boot? Why Laravel? Why not NestJS with a templating library?
Now the question is
If it's that good why it's not taking over many frameworks either backend or frontend
Like in my place no one using it
Because nothing can replace js, and it freedom to build your customize app tailored to your needs, lavaral is just too one sided, which is a risk for companies
It won’t take over unless all the 12 week boot camps start teaching it.
Laravel docs is great. However the article submenu is not sticky and I must always scroll up to see it again, which is annoying. 😒 I solved it by creating a custom stylesheet which makes the menu stick to the right side of the page. Much better experience! 😏
Have you tried making a PR for it ? It feels annoying honestly 😢
I like Laravel as a back-end Framework, that's it: Inertia is not a good solution to the integration issue.
Give me some suggestions.Currently i am learning MERN stack and have done html/css/js/react and now on next js. Should i have to learn Laravel or go for node.js like MERN stack is so saturated now
php and laravel are very powerful tools
While Laravel is fun, and for hobbiest. To be honest, the ecosystem, community ,libraries around React, Angular, Vue, NextJS are much much bigger. The prospect for Laravel in Enterprise apps is tiny
U shifted to PHP and Laravel after 6 years in React and NextJS
I never really “shift.” Different tasks take different tools. And some are more enjoyable that others (also subjective statement)
if you need simple things that's only be enough for small projects (like email as you said) yeah go use laravel, but it's never gonna be enough for big projects and if your program become popular your gonna face big issues
i use it on some fairly busy sites (several thousand visitors at peak times). no issues. granted its not millions of visitors but its a decent amout of users......
4:00, I'm on Laravel because of RoR. 😉
Love for Remix❤
I often wonder what laravel would look like if it was developed in a strongly typed language like saaaay C#
No, you must be out of your mind to say thats first time laravel user like it in 2024, because i dont. Its full of abstraction. Its not slow or bad and it has some level of community but i genuinely dont think you should start laravel in 2024 just because of the syntax and weird orm like Eloquent, personally i prefer something like sqlc or prisma.
And the server setup is a madness compared to js. You really need to dig up a lot of deps from years ago
Has anyone noticed the job market for Laravel drop or increase?
It's under the low-paid PHP jobs and there was a huge drop last year of Laravel/php related jobs
@@codernerd7076 should focus on MERN or React with Python?
@@codernerd7076 which would you recommend... MERN or python and react?
The job market has definitely seen a downturn, and Laravel seems to be struggling to maintain its relevance. It appears that they’re trying to revive interest by leveraging social media influencers for promotion. While Laravel is a decent framework, it’s extremely opinionated and built on top of PHP, which has a mixed reputation. Over the years, it has improved by incorporating elements from languages like C#, Java, and JavaScript. Personally, I enjoyed using Laravel up until version 7. However, the frequent major version releases one every year have become a significant burden, as they require constant updates to keep your applications up to date. Lack of built-in generics in PHP is one of the things that makes type-hinting in PHP a nightmare. They're still one step behind the big players like Java and C# when we talk about enterprise application.
@@yashuabaryosef4413 great nuanced answer! For large scale, it really does not hold up as well as the likes of Java/modern .net and for smaller, more agile teams…honestly I’d just go with rails now. You don’t have the same development pace in Laravel and despite rails’ reputation, it’s much less restrictive than Laravel and holds together better when you need to do novel things with the framework. If you’re just serving an API, I’d still probably go with rails, I prefer active record to eloquent, rails routing is immensely good and rails is also a little faster than Laravel.
Next is a Static Site Generator, Laravel is not
Yeah, i love JS sytanx but JS-land has nothing that can truly be considered "full stack"
So react + php? I want to learn php but always been told not to lol use next.js or etc but I cant deal with next.js
Laravel v5.8 + queue jobs features from the v8 was the best version of Laravel..
basically everything else is just hype inspired from non-stable JS world
I am learning laravel. Its very good, But using it as api for backend it gives less help. like no starter kit for api. there is breeze api but need to edit a lot to work with it for api. other problem i encountered is if i am using it as an api when i sent mail for reset password or mail verification i need to edit the code in appservice provider for appending frontend url. or it will send the link with backend url. I think laravel framwork is focusing on full stack using inertia . it gives less support in api development.
“The campfire app that came out recently” were you joking? lol😂
Never like Ruby either. Used Laravel off on and for years but haven't used it for about 5. Have to disagree about .Net. It may not have all the docs in one place but the support and training for it are everywhere.
Gotcha. I’m actually a huge fan of .NET
I'd love to know your thoughts on Nest JS
They just toke the Angular way and dropped it on top of Express/Fasify
@@codernerd7076 is that a good thing? a bad thing? How does it compare to laravel?
Nest is a little bit too niche when I last checked it out.
@TravisMedia Nah, check it out again. It's awesome.
Nestjs is basically express with a lot of sugar coat in angular style, the benefits is more towards DX rather than end user
Why don't we have frameworks like Laravel and Django for Javascript, is there something we don't know?
Angular?
AdonisJS. Haven’t looked at it in a while, but being the JS Laravel seemed to be the goal.
I use react pure client side with Django as my backend. It’s great. Except for migrations.
@@jasinrefiku2914angular isn't a a backend framework
We have. AdonisJS.
Still love next.js
I understand. It’s not going anywhere. In fact, it’s a necessity these days.
I barely understand how we are comparing react (basically frontend) with an MVC framework
What's you opinion on NestJS
What about angular?
Laravel is good
Laravel seems good but I m not a big fan of Livewire, sad.
I prefer my Rails and Hotwire framework for my personal projects.
I use adonis
I enjoyed the video, but the idea that "criticisms of PHP are unfounded" is just not true. Maybe dev's feedback should be heard and not dismissed as "hate". The same goes for JavaScript, PHP, NextJS, or any other language/technology. It's always easier to say "hater", than understand where the criticism comes from, because people's intentions are not bad most of the time, they're just expressing they're experience when using a language/technology.
It is unfounded most of the time because people compare it to the wrong things, and for being used for the wrong purposes. And hate? Who said anything about hate? It's just a language
i.e. PHP is slow...check out Rust. 🤔
The problem is not PHP, the problem is the entire development of the web and the browsers, it was unorganized and a technical mahem.
💯
I hope laravel wont became the next vercel or heroku
what's wrong with Vercel? i use them for my Vue apps??
How about springboot?