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.
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.
@@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.
@@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.
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.
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.
@@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.
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.
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.
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
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.
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!
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?
I don't like inertia cause every routes is a backend request... doesn't matter if it's a page like the about page which will never change and doesn't needs to be fetched every time but inertia just forces it
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.
@@aarondfrancis Oops, I'll make sure to watch the video till the end then lol 🙂 Kinda stopped watching it when you said Laravel vs React is a false dichotomy. I completely agree with this statement. Figured you will be talking about how to use React and Laravel together.
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 🎉
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!
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 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.
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!
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.
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
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!
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.
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.
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?
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.
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.
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.
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.
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.
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.
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.
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?
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.
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.
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.
one min silence for those who thinks php is a dead language..
proud to be a php laravel developer for a decade
sunken cost fallacy?
@@nymez6968 literally no
@@nymez6968 Cope
Seems to be more PHP jobs
@@Joshua.Developer more than what?
Another great video. Thank you!
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.
laracasts.com, for sure
What about react vs livewire?
Up to you! Mostly based on personal preference
@@aarondfrancis i mean livewire is also that much powerfull as react.. Or can u make any full stack project using laravel + livewire.
@@DEBUGENTITY You'd need some AlpineJS on the frontend for local only reactivity, but yeah, Livewire is pretty powerful
I love the take of "let's stop making everything X vs Y and instead use X and Y when appropriate"
This, everytime. I wonder why people want everything to be all or nothing
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.
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.
Watch me use react with laravel
@@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.
I was an early adopter of the Inertia with React and I can really enjoy seeing this combo gaining traction again these days.
Better than livewire?
@@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.
Same
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.
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.
I like you already 🤗
Remiss was a vocubulary that cought my fancy in this video. I had to look up its meaning.
Me too. He speaks very clearly.
I'm sold, following you from planetscale though i haven't used planetscale ever.
Thank you 😍
Me too 😊
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.
The old VILT stack. Easily my favorite.
With Arms Wide Open, Under ... Laravel. Welcome to this place, I'll show you everything - Aaron's Ringtone
😂 bravo
For a PHP developer like me who is primarily backend person; livewire is awesome! It's like writing php for front-end.
livewire is actually JS
@@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.
Please make A video about LARAVEL+HTMX supremacy
At this point, everything seems better than react
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.
Gosh this is such a good video. The intro made me laugh 😂
This is the content I’m here for!
Haha thank you
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.
Thank you Justin!!
I heard there was drama on xitter about react vs Laravel. And now this! Thanks for talking sense, Aaron
🫡
html+jquery
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
Livewire for the win.
Already have a running Laravel and vue. I will try later the react
you kind of look like Preston from the youtube channel "gentleman's gazette" lol, but less skinny
Less skinny... You mean fatter? 🧐
@@aarondfrancis ahahahahhaa I would never dare 🛐
Php jobs pay sh.t but knowing react you get 20% more upfront, so ok, although still not enough for me to touch frontend.
I have been using inertia with react and laravel.
Great right?
I have been using inertia with vue and laravel
Just here for the comments, especially from those brainwashed to believe you can't built anything with anything other than react.
Guys, hear me out. Laravel + Angular 😳
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.
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!
In my opinion, inertia joins the most powerful backend framework with the most powerful frontend library.
I wish Django had that
Django has Unicorn. And you can use inertia with Django.
love using inertia with vue
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?
Express is just a router. Laravel is a full stack framework
Laravel + Next.js = 🤯
yo bro im new in laravel but i love react but i love both
Nah, I prefer Vue.
That's fine
Kick ass combo
Good luck finding a better ecosystem than react's
@@thedavistheory7674 it's ok to like different things
@@aarondfrancis That guy is correct though.
Live wire or htmx for most cases
I Love laravel
React is only a frontend framework tho i don't understand the comparison
You're gonna love this video then!
I'm about to level up from WordPress to Laravel for my next project
HTMX mentioned!
I don't like inertia cause every routes is a backend request... doesn't matter if it's a page like the about page which will never change and doesn't needs to be fetched every time but inertia just forces it
Yup! It's great if you want your backend to handle routing (which I do)
Vs angular?
Great video 👍
Really enjoy the graphics. Nice step up in quality!
Thanks! That's all my cofounder, Producer Steve. He's the wizard
What a stupid comparison
Laravel and React are entirely used for different purposes
That's... that's the point of the video
php backend framework vs js frontend library... what? next video bugatti vs fanta?
Ooo good idea. Just gotta get my hands on a bugatti
Came here just to downvote such garbage content. "Laravel vs React:
And then what... did you watch it?
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.
Let’s face it the best frontend platform will be the one that AI can do the best
do not go gentle into that good night
What about Laravel vs. Nextjs? This will be a little less false dichotomy.
I cover that in this very video 🥰
@@aarondfrancis Oops, I'll make sure to watch the video till the end then lol 🙂 Kinda stopped watching it when you said Laravel vs React is a false dichotomy. I completely agree with this statement. Figured you will be talking about how to use React and Laravel together.
Happy with Next.js full stack.✨✨
Great! I'm happy for you
Is it sort of like Nuxt?
Why not Pocketbase + Astro?
I've never used either of those things
Say that to Theo from t3, lol, he things React is better than Laravel.
Haha oh I know
Plain php
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 🎉
Thank you for telling me! That's an encouragement
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!
Thank you!
so i must use both, thanks for clearing.
You're welcome! Glad it was helpful
219 views in 8 minutes, he fell off...
Edit: /s
Thanks for this awesome content Aaron!
Is that good or bad? I don't understand. I feel like it's good!
@@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!)
30 seconds into the video and you earned a Like
😮💨😮💨 thank you
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.
One can only cover so many chasms per video. And only the network chasm was relevant
@@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.
truck vs dolphin
did... did you watch the video?
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
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!
Laragon is cool
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.
thx
nice
Ah yes, apples vs oranges let's gooo
Did... you watch it
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
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!
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.
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.
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?
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.
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.
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.
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.
Mr. Dunphy comes for the rescue ❤
Everyone's favorite sitcom / youtube dad
Thank you sir ❤❤
do you have any course for using laravel, inertia and vue.js???
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.
I haven't! I'm sure it just doesn't line up with what they personally use. Just a guess though
Laravel is still very much slept on by a large chunk of the dev community. We use it explicitly, big web apps, its great.
Another great video! I’ve been using your videos to learn Laravel and your videos have made growing my application’s features much easier.
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.
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.
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.
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
This guy wants end the backend-frontend war
God willing
Thank you for your videos! People like you reassure me that php/laravel is awesome and leave the haters be
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.
Sick. Might get the opportunity to make a new application for a client soon, and I think we'll probably try this.
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?
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.
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.
thanks for explaining fundamentally i loved the format thank you
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.
👍
This aligns with my favourite approach exactly! Laravel inertia and Vue are a powerhouse for full stack development!
Amazing! Imagine telling a team that’s used to doing express api’s for frontends about this 😂
This is THE BEST visualization for making the right choice!!!
Hahahaha nice intro, the thumbnail had me thinking "what about Laravel & React"