Laravel vs React

Laravel + Inertia + React / Vue: laravel.com/docs/11.x/starter...
Laravel + NextJS: github.com/laravel/breeze-next
Livewire: livewire.laravel.com
InertiaJS: inertiajs.com/
Advanced Inertia (with end-to-end typesafety): advanced-inertia.com/

[@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

[@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.

[@JohnnyHandsomeCapital]

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.

[@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!!

[@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 🤗

[@liorocks]

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

[@DoctorSoulis]

Better than livewire?

[@liorocks]

​@@DoctorSoulis 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

[@nenmeet]

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

[@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.

[@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.

[@andyhinkle]

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

[@aarondfrancis]

😂 bravo

[@Ashish_singh_dev]

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

[@aarondfrancis]

Thank you 😍

[@shravanuchil]

Me too 😊

[@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

[@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.

[@fadlihidayatullah2052]

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

[@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.

[@adammenczykowski]

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

[@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

[@yordanmilchev8706]

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

[@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!

[@JeremyAndersonBoise]

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

[@aarondfrancis]

🫡

[@danielefarriciello7239]

nice and fluent explanation, thank you so much

[@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!

[@JosephCodette]

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

[@Stoney_Eagle]

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

[@cowgod77]

Really enjoy the graphics. Nice step up in quality!

[@aarondfrancis]

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

[@peteremad5228]

love using inertia with vue

[@wtalkie]

Great explanation. Keep up the good work.

[@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.

[@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

[@jonathanvioleta3578]

This is exactly what im looking for 🔥

[@alexandruaxentioi3006]

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

[@DanelonNicolas]

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

[@DailyGuideVideos]

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

[@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.

[@citricguy]

Another great video. Thank you!

[@southernfriedhackers6475]

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

[@ruslansteiger]

Incredible explanation 👏

[@tecsmith_info]

About time we got some props for Laravel + JS

[@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

[@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?

[@ernestharuna]

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

[@SimoneFolador]

Great video, couldn't agree more!

[@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

[@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?

[@iapv]

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

[@k98killer]

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

[@parihar-shashwat]

I have been using inertia with react and laravel.

[@aarondfrancis]

Great right?

[@gessegoncalves6493]

I have been using inertia with vue and laravel

[@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!

[@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.

[@hassanmehmood8711]

30 seconds into the video and you earned a Like

[@aarondfrancis]

😮‍💨😮‍💨 thank you

[@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.

[@hyphenzero]

Laravel + Next.js = 🤯

[@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

[@CodeX-xyxy]

Laravel + Inertia feels so goooood

[@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

[@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.

[@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.

[@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.

[@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!

[@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!

[@buddy.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

[@havecodesoft]

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.

[@___Kevin]

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

[@christophrumpel]

Great video 👍

[@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.

[@tsubasateacher]

HTMX mentioned!

[@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.

[@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.

[@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

[@stylrart]

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

[@aarondfrancis]

Cool!

[@keyonlewis7574]

I am using nextjs as my backend for a flutter app

[@NFM-nb7dl]

what about laravel with Angular ?

[@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.

[@Prejudice182]

HTMX mentioned, lets go!

[@mojahidulislamemon371]

Please make A video about LARAVEL+HTMX supremacy

[@DoubleOBond]

Livewire for the win.

[@HijabiCoder]

Aneamic backend got me 😂

[@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()

[@matheusnb99]

Can someone please explain why is laravel a powerful backend and nextjs is not ? I've seen that schema before (4:33) but I don't really understand what laravel has that can't be done with Nextjs

[@aarondfrancis]

Laravel handles queues, migrations, ORMs, mail, cron, auth, etc etc

[@matheusnb99]

@@aarondfrancisI mean, out of the box yeah but can't you just add some other packages to do all that?

[@assertchris]

Love the polish.

[@aarondfrancis]

We can only thank Producer Stever for that 😮‍💨

[@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.

[@rawallon]

I wish Django had that

[@jmon24ify]

Django has Unicorn. And you can use inertia with Django.

[@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.

[@kc-fr3qp]

Curious where you were going with a vs video because my brain thought shouldn't you just use them together? Php and Javascript have been best of friends since jquery. Glad I was right.

[@feelingfun5149]

Cool!

[@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.

[@TheArmanist]

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

[@aarondfrancis]

😉

[@bosphoramus]

love inertia

[@vishaldinesh]

Mr. Dunphy comes for the rescue ❤

[@aarondfrancis]

Everyone's favorite sitcom / youtube dad

[@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.

[@M1a2n3o43]

So i can do this with django aswell? Wow will look into it

[@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.

[@JustSteveKing]

Need more APIs! 😜

[@naspy971]

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

[@thedailycutline278]

Nextjs solves seo and performance by rendering html from the server and hydrating client side interactive code from react, this makes your website have a good seo and performace but the way laravel works with react, even by bridging the network gap, still seo will be hit hard because the fronted will still be pure react.

[@aarondfrancis]

You can do SSG with Inertia 🥰

[@Dino-Kupinic]

@@aarondfrancis what about SSR?

[@aarondfrancis]

Hm that's what I meant! Inertia does SSR

[@thedailycutline278]

So what you mean is that inertia hydrates php server side html to react via inertia which is then prerendered with react interactivity , thats cool, i guess it will be somehow slow as to me inertia looks like a really different layer that sits between react and php which are 2 different languages, unlike how next solves it without a middle layer like inertia because javascript is able to run on the server and frontend.

[@aarondfrancis]

@@thedailycutline278 inertiajs.com/server-side-rendering

[@jonanthonii]

im almost a year using php without no knowledge in frameworks like laravel. zero knowledge with react and vue too but i really wanna expand my knowledge but idk how to start.

[@aarondfrancis]

laracasts.com, for sure

[@estebanmurcia8451]

I would expect that Laravel being a little oop based it would also support angular

[@aarondfrancis]

It might... but I haven't seen any first-party support options for Angular!

[@estebanmurcia8451]

@@aarondfrancisSadly 😥

[@monciego]

❤

[@JagdeepSinghKalsi]

I would like to have a conversation with you around Laravel+Next.js, focused on identifying and resolving "understanding" barriers between backend and frontend teams at an organisational level. I know you wouldn't have time to do this (considering you have a zillion things to do), but I'd really like to pick your brain. I so wish it could happen some day.

[@aarondfrancis]

I don't know enough about Next.js to say for sure. And I think using Inertia + React would be my preference (actually Vue, but same same)

[@swordali]

thx nice

[@QueeeeenZ]

But does Laravel work together with Next.js because Next is awesome and Laravel is awesome

[@aarondfrancis]

Yes... I say that in the video 😂 And there's a link in the description