Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
As a beginner, I can see that Inertia does help and save time, but what about when you're already experienced - do you guys with experience with Laravel think Inertia is going to really help in the long term or I should learn the old fashioned way of Laravel + Vue + API? Pros and Cons from you experienced guys?
You have to think about it from the project perspective. You shouldn't stick and force one stack if you see that it might be wrong for that specific project.
Laracasts is built with Laravel + Inertia. For me, that is still a very young stack and I would carefully analyze if it can fulfill all project requirements. If there are no concerns then I would use Inertia because it saves time. If not, then I would go with the traditional setup Laravel API + Vue.
@stacker How many questions are you going to ask about the same thing…?
Learn the basics, then build on that. Build something using controllers and Blade views. Then look at maybe making things dynamic with a sprinkling of JavaScript. Then look at more advanced JavaScript patterns like SPAs.
Stop worrying about technologies and just build something.
I had no idea @stacker asked the same question over and over again. @martinbean are you stalking @stacker? 🤣
Haha I asked so many questions lately that @martinbean didn't need to stalk me to see it. 😂🤣. But I just last week started with Laravel after using only PHP and discovered a whole new world.. so many questions haha. But he's right though lol I did ask quite a lot (and of the same nature). By the way you think they will add a Tailwind sub-forum here?
By the way you think they will add a Tailwind sub-forum here?
What would be the advantage compared to now? You can see that bunch of people doesn't place their discussions into correct channels.
Please or to participate in this conversation.