Laravel vs React

[@ajlive6737]

one min silence for those who thinks php is a dead language.. proud to be a php laravel developer for a decade

[@nymez6968]

sunken cost fallacy?

[@m.moonsie]

@@nymez6968 literally no

[@nou4605]

@@nymez6968 Cope

[@Joshua.Developer]

Seems to be more PHP jobs

[@nymez6968]

@@Joshua.Developer more than what?

[@millennia]

As a non-native English speaker, I learn new words every time I watch your videos! Today I learnt the words: remiss and dichotomy. :) Thank you Aaron! Informative video as usual.

[@adeyemiowolabi6062]

I like you already 🤗

[@kennethkipchumba2532]

Remiss was a vocubulary that cought my fancy in this video. I had to look up its meaning.

[@kitteemail12]

Me too. He speaks very clearly.

[@wcrb15]

I love the take of "let's stop making everything X vs Y and instead use X and Y when appropriate"

[@disgruntleddev]

This, everytime. I wonder why people want everything to be all or nothing

[@jordixboy]

thats the whole premise of being a software engineer, if you're a fanboy about a certain technology, then you're not a good software engineer.

[@JohannSiemens85]

Yeah, i think the devspace is super poluted with absolutes. I always thought of tech in general as a toolkit to solve problems. I don't care which tool fits the best, i just use the one i know solves the problem the best way and try to learn new tools regularly.

[@MrSofazocker]

Watch me use react with laravel

[@MrSofazocker]

@@jordixboy Yep, my mantra is "Don't get yourself bullied". If you can't work outside of a framework to get sh* done when sh*t hits the fan, you're a script kiddie and nothing else.

[@MrErdkamp]

Started a Laravel/Inertia/Vue project this week. I am still very much slower in writing php, but you can just 'feel' how powerful this stack is.

[@r1konTheAutomator]

The old VILT stack. Easily my favorite.

[@liorocks]

I was an early adopter of the Inertia with React and I can really enjoy seeing this combo gaining traction again these days.

[@Soulis98]

Better than livewire?

[@liorocks]

​@@Soulis98 If you're coming with a PHP background, then Livewire might be easier to understand and be a better choice in some cases. If you need high interactive client side application, then using React or Vue with Inertia would be a better alternative. Inertia caught my eye few years ago with it's possibility of creating SPA-like websites with my favorite tech stack of choice: Laravel and React. And I've done multiple client projects with it successfully. Everything seems so natural, intuitive and easy to use/integrate compared to traditional way of API + SPA communication. And as a solo engineer on a project, it was a perfect choice for me. Livewire on the hand I think was a missing piece of the Laravel ecosystem. Same technique was used by Github for many years, when on some action rendering is happening on backend and html sent to the browser, instead of json. Plus you get blade syntax support out-of-box, where u can use directives like `@can` and so on. With Inertia, you have to implement that part on your own in javascript. I've been actively using both of them on my projects and all I can say, that they made my job more enjoyable and coding fun again. I love what both Jonathan and Caleb did for the ecosystem and I think both of these packages are very underrated today.

[@tecsmith_info]

Same

[@JustinJackson]

This is the best explanation I've seen for how the different layers (back end, network, front end) work together and which frameworks cover which parts. Also, love how you visualized where Livewire sits in all of this. Really well done! Thank you.

[@aarondfrancis]

Thank you Justin!!

[@mahmoudmousa2405]

Oh god, I can't believe it. I am so happy someone popular is actually clearing up those weird concepts that FE people have smashing NEXTJS everywhere and calling it full stack

[@nenmeet]

For a PHP developer like me who is primarily backend person; livewire is awesome! It's like writing php for front-end.

[@hakanaya]

livewire is actually JS

[@Cainny]

​@@hakanayayes he said it in the video lol. Livewire handles every single part of the JS without writing js. All ajax requests are handled under the hood.

[@groovebird812]

What are the differences between livewire and inertia? There are so many libs and it is difficult to find the exact boundary

[@nenmeet]

@@groovebird812 My understanding is that, inertia is a bridge that connects Javascript front-end to backend like, laravel django etc, while, livewire is more like a mini framework specifically designed to work with laravel to handle reactive part of front-end.

[@ivan.jeremic]

so server components for php? :P

[@Ashish_singh_dev]

I'm sold, following you from planetscale though i haven't used planetscale ever.

[@aarondfrancis]

Thank you 😍

[@shravanuchil]

Me too 😊

[@robrobob]

This is so great! You are such a good advocate for PHP. Please keep doing what you're doing! Just let people use what works for them. I've had a bit of JS burnout lately and so I've gone back to using PHP but I've gone ultra minimalist this time with zero JS on the front-end and even using a classless CSS framework that is literally just a "drop-in and forget" solution to styling. I'm using good ol' Smarty to render HTML in PHP and the resulting HTML (with zero JS and zero CSS classes) is just so incredibly pure and simple. Admittedly, you do sacrifice A LOT by not having any JS on the front-end but the simplicity is so freeing! I'm getting features done faster than I ever have before. It's awesome!

[@JeremyAndersonBoise]

I heard there was drama on xitter about react vs Laravel. And now this! Thanks for talking sense, Aaron

[@aarondfrancis]

🫡

[@raenastra]

Using the term "center-stack framework" to describe recent JS frameworks is so good. I've been writing a lot of SvelteKit recently and wondered why the backend functionality seemed so sparse, even though it's often called full-stack. Definitely looking into Laravel for my next project.

[@andyhinkle]

With Arms Wide Open, Under ... Laravel. Welcome to this place, I'll show you everything - Aaron's Ringtone

[@aarondfrancis]

😂 bravo

[@valid_]

Dev with >15 years experience. Your content is refreshing man. Both the positivity but also technical knowledge is greatly appreciated. You’re getting me a ton more interested in php and laravel. I only knew PHP from old Zend days… insane updates. Quickest tech YTer subscribe in awhile 🎉

[@aarondfrancis]

Thank you for telling me! That's an encouragement

[@tiagobordin6580]

In other words, all we need for Web Dev is PHP for back and JS for Front End. Like it was 20 years ago. For me, this is the perfect Mix.

[@nicodemosgomes5789]

I think this video really necessary today. I use Laravel 9 years already and started using React in the v15, and I see a huge hate on the Laravel community about React that I can't understand. Laravel is the most amazing framework in my opinion and I think that the power of the interaction and management of React complements this ecosystem so well.

[@nikitapashinsky]

As someone who is not a professional developer (I know some JS and a little bit of React), this is such a great overview of all the different parts that make up web app development! Like pieces of a puzzle coming together. Thank you Aaron!

[@alejonanez]

Gosh this is such a good video. The intro made me laugh 😂 This is the content I’m here for!

[@aarondfrancis]

Haha thank you

[@StefanMalic]

Hey Aaron, I've been using Inertia for a few months now, and I gotta say it's a joy to work with. It's really minimal in a sense that it gives you the basic Laravel/React bridge + some pretty nice utility components, such as InertiaLink. It doesn't make you dependent on itself, like a framework would, so you're still writing React/Vue/Svelte code.

[@atalocke]

Another great video! I’ve been using your videos to learn Laravel and your videos have made growing my application’s features much easier.

[@lafanter]

Great video! It makes it very very easy to understand the whole eco system and describe what is what, where it belongs and what's it's role it for someone like me who is new and doesn't know what all these technologies are.

[@adammenczykowski]

This aligns with my favourite approach exactly! Laravel inertia and Vue are a powerhouse for full stack development!

[@anderskozuch7838]

Aaron I am big fan of yours and want to say thanks for your efforts! I am a self taught noob doing coding for fun, and you have always given me a lot of inspiration when I watch your videos:) Have a great day!

[@aarondfrancis]

Thank you!

[@picklebrownie]

Thanks for posting. I'm a PHP dev looking to explore something newer/cutting edge, and this helps me on the right path. Tying together Laravel and React is going to make me such a powerful developer.

[@alexanderkrist95]

Amazing! Imagine telling a team that’s used to doing express api’s for frontends about this 😂

[@cowgod77]

Really enjoy the graphics. Nice step up in quality!

[@aarondfrancis]

Thanks! That's all my cofounder, Producer Steve. He's the wizard

[@MjrGeneralGhost]

I mean if I am starting a new project, I personally prefer to not to mix backend and frontend. It's always better to create an API and connecting front and back together, this way in the future you can build mobile apps using the same backend, you can hire easier since you are using mainstream tools and framework (i. e. Vue, React) instead of finding people who know edge cases. There are hundreds of reason why not to do this, but it may be a good for some edge cases.

[@Stoney_Eagle]

This is THE BEST visualization for making the right choice!!!

[@ernestharuna]

Hahahaha nice intro, the thumbnail had me thinking "what about Laravel & React"

[@iapv]

In my opinion, inertia joins the most powerful backend framework with the most powerful frontend library.

[@peteremad5228]

love using inertia with vue

[@tecsmith_info]

About time we got some props for Laravel + JS

[@edventuretech]

I personally love Livewire. It's pretty easy to start the first demo for clients. I don't have to mess up with building back-end API or fetching API in front-end. All I need is just Livewire components Of course, I also use React, Vue or sometime Angular. It depends on requirements and many other reasons. It doesn't have to be this tool or that tool. It's how we mix up and make it works for our clients!

[@southernfriedhackers]

Laravel is still very much slept on by a large chunk of the dev community. We use it explicitly, big web apps, its great.

[@DoubleOBond]

Livewire for the win.

[@JosephCodette]

Thank you for your videos! People like you reassure me that php/laravel is awesome and leave the haters be

[@naspy971]

Never heard the word "Chasm" that many times within a few minutes

[@isaiahproctor8070]

Been using react and Laravel a lot lately but been a little disappointed at the lack of adoption of it. Glad to see that slowly changing!

[@hassanmehmood8711]

30 seconds into the video and you earned a Like

[@aarondfrancis]

😮‍💨😮‍💨 thank you

[@parihar-shashwat]

I have been using inertia with react and laravel.

[@aarondfrancis]

Great right?

[@gessegoncalves6493]

I have been using inertia with vue and laravel

[@Nailed_It_Tutorials]

Which stack is better for making startups: vue+laravel/vue+express? Is there any difference what to pick up or the possibilities are the same with both?

[@aarondfrancis]

Express is just a router. Laravel is a full stack framework

[@pasizdobrekuce]

I've never understood why? Why, if you have available all of the periphenalia in Laravel itself, would you want to add more javascript just for the sake or the snappy-ness? What is exactly wrong with "old school" approach of building web apps? I don't get it.

[@s1ckret]

Laravel is the best ecosystem I ever experienced for building MPA. In other languages (C, Java, Js, Python, Go) I always need to glue together different 3rd party libs. I wish we had smth complete like Laravel for Java or Go.

[@jaspergorchov]

Laravel + Next.js = 🤯

[@scuraluis]

Great video Aaron. You explain things very clear. Since Inertia.js eliminates the whole API creation, when would you say is still recommended to use laravel as API backend only and fronted separately?

[@aarondfrancis]

If you were using Next or Nuxt or needed an API for other reasons beyond your own frontend

[@suikolaravel]

I really love your videos! Hopefully you post more content for us to learn

[@yordanmilchev]

Very informative on stuff I already did know but someone that is fresh to this it's a valuable video

[@k98killer]

Sick. Might get the opportunity to make a new application for a client soon, and I think we'll probably try this.

[@SuchismitaBasu-bj8rm]

I learned a lot from this video and gained some clarity on a problem we are currently facing with one of our projects. Our team worked on a project that uses Laravel as the API backend and Vue2/Nuxt2 as the frontend. With the release of Nuxt3, there have been significant changes, and we are struggling to decide how to keep the project updated without rewriting the entire codebase. Since all of the developers on our team are fluent in Vue.js, we still want to use it as the frontend framework. After initial discussions, we are leaning towards using Laravel + Inertia + Vue, but we are open to any other suggestions. Any input is highly appreciated.

[@mornemarais4198]

thanks for explaining fundamentally i loved the format thank you

[@TheArmanist]

The video started with really awesome conversation until the phone call cut it.. love to hear the rest :))

[@aarondfrancis]

😉

[@Leonhart_93]

Yep, I use a combination of Laravel and React, without making it a single page application, but instead having a react build for every module in the application, which I then link statically.

[@aarondfrancis]

Ooo interesting

[@Leonhart_93]

@@aarondfrancis Yeah, I have created a webpack builder that outputs multiple react builds at once, one for each module in my app. The react framework itself is a separate file, since it's shared between them and it should be cached only once. Like that I also manage to keep my bundle size small and fast per page, and the users probably don't navigate through each module all the time for everything to be loaded at once.

[@Xamnalim]

Inertia officially supports only Laravel and Ruby adapters (as they say in the documentation). Other adapters are community maintained. F.e. symfony adapter repo is currently archived and looking for a new maintainer.

[@Xamnalim]

They don't say they have adapter for django, but have a interia-django repo on their github account - that's odd

[@aarondfrancis]

Huh that is interesting. I wonder if the docs are just outdated for that section

[@arashshahabi853]

Hey Aaron. Have you ever asked Taylor and others why jetstream starter kit does not ship with inertia and react? I really like having that option as well as breeze.

[@aarondfrancis]

I haven't! I'm sure it just doesn't line up with what they personally use. Just a guess though

[@kizunaastin5308]

inertia js is the key, Laravel solid backend with queues, validation, authentication, MVC, support multiple db connection it could be mysql and mongodb or etc

[@wtalkie]

Great explanation. Keep up the good work.

[@DanelonNicolas]

nice one, love this type of videos 😁 love the overview that invite you to investigate ❤

[@ahmadhusain9075]

Thank you sir ❤❤ do you have any course for using laravel, inertia and vue.js???

[@gabrielranea]

I think the problem sometimes in this discussion is people trying to set the "default" framework for frontend as if just React exists, ignoring Vue.js or even HTMX... Not just because it is currently the largest used that it's the best framework, just see how much jQuery reigned and how it is seen now.

[@jcc5018]

can you explain what sorts of interactivity react or vue provides that would be worth the extra setup? I'm not a FE developer, but so far I've been able to accomplish most everything I need with laravel and livewire, though still struggling with some parts. I don't know when I should consider alternatives such as react or vue with inertia and I hate having to keep learning new tech stacks when i still havent mastered Laravel itself. It'd be great if I had examples of what these tools are actually good for opposed to alternatives? Perhaps some samples of interactive components being built with the 3 systems (vue, react, livewire) to gauge speed and complexity of getting things set up?

[@aarondfrancis]

Honestly I think you can get as far as you need to go with Livewire and a bit of Alpine. Only the most complex frontends would need Vue or React at this point

[@muhammadhanzala3556]

Happy with Next.js full stack.✨✨

[@aarondfrancis]

Great! I'm happy for you

[@___Kevin]

I'm about to level up from WordPress to Laravel for my next project

[@sofianesofiane212]

I'm 43 yrs, i'v been started learning php to learn laraval , hopefully to find a job as developper

[@danielefarriciello7239]

nice and fluent explanation, thank you so much

[@br3nto]

It feels a bit weird to talk about “Network chasm”. This chasm exists in many places in software systems architecture: the file system, memory, socket programming, decoupled modules, args and environment varsity passed to a running program, config files, all of these are “chasms” that move from one context to another. The “network chasm” isn’t really that special.

[@aarondfrancis]

One can only cover so many chasms per video. And only the network chasm was relevant

[@br3nto]

@@aarondfrancis My comments are just social commentary on the industry perception that you highlighted in your vid. I’m just saying that it’s less of a “chasm”, and more like a “crack” or “gap” that is common and has been filled many times. “Chasm” makes it seem so big and scary, which it’s not when you really think about it.

[@roselyn123]

Already have a running Laravel and vue. I will try later the react

[@Aaron_17]

I started a Laravel course on Udemy but recently stopped to learn React. I'm hoping to get my first dev job sometime this year, and it looks like most entry-level jobs in Canada seem to prioritize front end skills, so maybe React might be considered a more valuable skillset? Btw kudos for knowing what a false dichotomy is, did you by chance study philosophy?

[@thedelanyo]

Wasn't it so from ages? Where the backend could be able to generate initial HTML page and then serve the browser? I guess when ReactJs first came, it wanted to push "everything frontend" but nowadays realized, some stuffs are for the backstage. Sveltekit pioneered this onset and I love its implementation.

[@m4rkbello]

I had my ReactJS, Redux, Axios, Laravel (REXAL STACK) but I would love to go this one VILT STACK OR RILT STACK OR NILT stack

[@panh141298]

Wonderful video overall but I think the default MVC Laravel diagram contradicts your definition. If frontend is code that runs on the client, then Blade is not frontend even if it is UI programming. I think MVC Laravel doesn't have a chasm, it's just that all the UI work is done through HTML responses. So that templating engine part you mentioned is actually part of the Network layer and very much the exact model of how websites used to be, hence Multi Page Applications and HyperText Transfer Protocol. You're completely correct about the rest though: with network-driven UI that doesn't reach into frontend capabilities, you can only do forms and links as far as interactivity goes, and more interactive Singe Page Applications necessitate client-side React/JavaScript.

[@pinoniq]

This also goes for Next.js, Nuxt, Remix, ... They all do server-side rendering and send the HTML over the network. It's simply the most efficient way of sending HTML to a client. Since thats what the protocol was designed for in the first place.

[@saloni6242]

so i must use both, thanks for clearing.

[@aarondfrancis]

You're welcome! Glad it was helpful

[@vishaldinesh]

Mr. Dunphy comes for the rescue ❤

[@aarondfrancis]

Everyone's favorite sitcom / youtube dad

[@nyambe]

Is it sort of like Nuxt?

[@jonathanvioleta3578]

This is exactly what im looking for 🔥

[@msnegurski]

actually would be great if Laravel had some sort of RPC library to communicate with frontend, like Livewire without templating or Inertia without routing. That way you could pair Laravel with any frontend without need for specific adapters

[@aarondfrancis]

Hmmm that's an interesting idea. Do you know of any prior art here?

[@msnegurski]

@@aarondfrancis there is nothing ready made. we are using Next frontend, Expo mobile app with Laravel backend and sort of stitch it together with laravel data and typescript transformer by spatie, so its kinda typesafe end to end but still requires a lot of boilerplating with setting up controllers, frontend->backend fetch calls etc. basically works as proof of concept but would be nice if laravel had something that wraps it all up with nice api, would be great win for ecosystem IMO

[@aarondfrancis]

@@msnegurski Extremely interesting... I'll see if I can wrap my head around it!

[@iamboris]

​ @aarondfrancis Sounds like a concept I hacked around some time ago. const component = useComponent('edit-product) component.product.name = 'Updated value' component.save()

[@Borg434]

We use Laravel on the back end and Vue on the front. Works pretty well. We've done it for a while. However, we are moving to fully NextJS. Why? It's reducing mental load by getting rid of PHP and only working in JS everywhere. Life is easier. We are more productive.

[@citricguy]

Another great video. Thank you!

[@kuunibyou7642]

Can someone elaborate more about the network part? Does laravel route while rendering blade file, can also pass data directly from database model? Or is it something else entirely?

[@stylrart]

Holy moly. I use Payload CMS ( build on Nextjs) with a MongoDB and a Nextjs Frontend - done.

[@aarondfrancis]

Cool!

[@DevlogBill]

on the subject of PHP. Last time I programmed with PHP you needed either XAMPP or MAMP to run your PHP code. Is this still the only method to run your PHP application or has PHP modernized where you can run it independently without XAMP or MAMP? Haven't used PHP in a while maybe things have changed?

[@aarondfrancis]

Nah you can run it normally. Mac has PHP built in, but you can use homebrew to get multiple versions. My personal recommendation would be using Laravel Herd at herd.laravel.com. I have a video on that here kzbin.info/www/bejne/qYqVcml3fKtopdU

[@DevlogBill]

@@aarondfrancis Thanks for the recommendation! I will try this on my mac. I also program on a Linux distro known as Cinnamon Mint which is Debian based. I will look online I am pretty sure if mac has this most likely there is something out there for Linux, thanks once again.

[@christianm4906]

At this point, everything seems better than react

[@Prejudice182]

HTMX mentioned, lets go!

[@sabriayadi8748]

Laravel + Inertia + Vue js 3 are the best for me

[@gillesashley9314]

I feel this debates depend on tons of factors. Your heart might say Laravel, your mind might say React due to the job market.

[@aarondfrancis]

That's fine! React works great with Laravel

[@ruslansteiger]

Incredible explanation 👏

[@thisisroushan_1337]

I've been developing with Laravel and Vue/React for over 4+ years now but I have to admit, I have never used Inertia. Something about it just seems hard to get into, so if there's a great (and free) course on it, I'd love to know :)

[@aarondfrancis]

I only know of Laracasts!

[@RobertoDuransh]

This guy wants end the backend-frontend war

[@aarondfrancis]

God willing

[@duckeggcarbonara]

219 views in 8 minutes, he fell off... Edit: /s Thanks for this awesome content Aaron!

[@aarondfrancis]

Is that good or bad? I don't understand. I feel like it's good!

[@duckeggcarbonara]

@@aarondfrancis Better see a million views in 30 seconds next time, bud. (I'm kidding. It's awesome! Love your content brother, please keep it up!)

[@JeremyAndersonBoise]

Wait a minute, Livewire works with htmx? (Edit: I was wrong) I have been doing htmx and blade, with a tiny bit of Alpine. Love it.

[@aarondfrancis]

Ah sorry, no. Livewire is *like* HTMX, Liveview, etc.

[@JeremyAndersonBoise]

@@aarondfrancis I misheard that, no worry. Thanks! I love htmx a lot.

[@cb73]

I’ve been developing apps in Laravel from 2015 to about a year ago. It does fill a huge need but I think the deployment picture still isn’t fully developed at least not in tandem with the JavaScript world.

[@SimoneFolador]

Great video, couldn't agree more!

[@HijabiCoder]

Aneamic backend got me 😂

[@christophrumpel]

Great video 👍

[@siya.abc123]

How will react 19 affect inertia? I'm not a php user but interested to know Edit I asked the question before you spoke about Next.js. please ignore

[@travisricker]

Here is my pro tip: Use Vue or React and try to use as few packages as possible. Then use Inertia with Laravel and try to only use Laravel first party packages.

[@aarondfrancis]

This is a good tip! 🫡

[@bdemon245]

Please make A video about LARAVEL+HTMX supremacy

[@hab_tech]

I am using react as my frontend and laravel as a backend but unfortunately there is no comprehensive tutorial about React and Laravel using inertia js. Jefferey have with Vue but no body with React.

[@keyonlewis7574]

I am using nextjs as my backend for a flutter app

[@RobinGiel]

Nextjs can be used as a backed and front-end. I don't see why you need an extra backend

[@aarondfrancis]

Database, auth, queues, ORM, mail, cron, console commands, etc etc etc

[@RobinGiel]

@@aarondfrancis okay that's a good point. I'm nowadays using Nextjs with Supabase. But maybe I should try Laravel just to see what I'm missing out. I was a PHP developer in the past, maybe this can be a great way to pick it up again. Thanks for the vid 💯

[@IvanRandomDude]

Because if you use Next you will eventually need 10 SaaS subscriptions to cover it's missing backend functionalities. There's a reason you are using Supabase. Supabase is your actual backend, NextJS is just a proxy for it.

[@Kopetefish]

There’s some really old issues on the inertia github repo that are seemingly ignored. I wouldn’t want to start a new project with it.