Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello everyone,
I'm Amil Murselovic, and I've been learning Laravel for the past months. I'm reaching out to this community to gain some insights into an aspect of Laravel that has piqued my curiosity.
As we know, Laravel is predominantly a backend framework, but it includes Blade, a templating engine typically used for traditional server-side rendered pages. Given the modern trend towards using Laravel in combination with front-end frameworks like Vue.js for more dynamic applications, I'm curious about the continued role and relevance of Blade in Laravel's ecosystem.
My questions to the community are:
Why does the course "Laravel from scratch" spend so much time using Blade instead of pairing it with some front-end framework?
Maybe, that can answer also these questions below: Why was Blade included in Laravel, considering its traditional use in a landscape that's rapidly evolving towards API-driven architectures? Does Blade offer unique advantages in certain scenarios compared to using Laravel purely as a backend?
Maybe, this can be answered by Jeffrey Way :)
@amil_murselovic You make as if Blade is obsolete. It’s not. And it’s included in Laravel for that very reason.
There are plenty of “traditional” server-rendered applications being written with Laravel that use Blade templates and haven’t jumped on the “SPA” hype train.
@martinbean And what is the advantage of using it?
@amil_murselovic What do you mean, what is the advantage of using it? Advantage as opposed to what?
@martinbean, advantages in terms of using Blade instead of JavaScript frameworks. As you stated, 'There are plenty of “traditional” server-rendered applications being written with Laravel that use Blade templates.'
I am just curious, what are its advantages in comparison to front-end frameworks? :)
considering its traditional use in a landscape that's rapidly evolving towards API-driven architectures?
Many of these api apps I see many people doing should really be regular web apps.
Do an api only when needed.
Also blade or php can be used as the template in an API. So whether an api or regular web app it doesn't matter.
Why does the course "Laravel from scratch" spend so much time using Blade instead of pairing it with some front-end framework?
Because this is a php framework. The Laravel from Scratch series is for people new to php and mvc, to teach the basics of using the framework. Can you imagine the complexity necessary to introduce into a beginner's course something like react or vue together with client authentication and apis and build processes whilst simultaneously teaching javascript?
And how many comments would there be like why did you choose X over Y, and can you do a from scratch series using Z (insert frontend framework of the month ).
There are specialised courses for these topics, but you should understand the basics first
As for the overhyped 'popularity' of frontend frameworks, all I see is people struggling and talking about the steep learning curve, whilst the rest of us just get on with it.
@Snapey, I think that when covering the basics, using JavaScript frameworks should also be mentioned, as they are a crucial part of development today.
@amil_murselovic in your opinion
@Snapey, here everything is subjective to one's opinion. I'm just expressing mine.
@amil_murselovic but you are not asking the pros and cons of frontend js frameworks versus blade, you are positioning it as beginners should be forced to learn a front-end js framework.
I don't know javascript and do very well with blade. Thank God for blade
@Bogey blade is just php template.
@jlrdw the original poster is talking about trends that go toward using javascript front-end frameworks... I don't know javascript, so I would be lost in a javascript front-end, and I'm happy to use the blade template engine to power my front-end. Why would you think I was talking about blade as a programming language? I wasn't born yesterday.
@Bogey in my opinion, you should start learning how to work with the DOM.
I suggest the long learning curve first and not livewire.
Later if you want livewire fine.
I suggest this, because at times it's good to update an element without full page reload prior to submit.
I even suggest learning server fetched partials, extremely useful.
https://laracasts.com/series/javascript-techniques-for-server-side-developers/episodes/1
I don't like some of the js frameworks, I use regular js and fetch js.
@jlrdw no reply needed except you are totally off topic as per....
@Snapey in the original question was:
Why does the course "Laravel from scratch" spend so much time using Blade instead of pairing it with some front-end framework?
Later @bogey
I don't know javascript and do very well with blade. Thank God for blade
So it's a sub-topic.
I was only trying to encourage someone to take the longer, harder learning prior to using livewire.
My reasons were: Knowing the DOM and using javascript and (fetch js or other) would carry over to any language (.net core, java ee, jakarta ee, spring, etc).
So believe it or not, I was only trying to help @bogey deeply learn instead of (at some point) reaching for livewire first.
Because eventually he or she will need to manipulate the DOM.
I encourage @jeffreyway to review my above reply, as when I see a spot to possibly help someone I take it.
So I am sorry if I looked at it as a sub-topic.
Why does the course "Laravel from scratch" spend so much time using Blade instead of pairing it with some front-end framework?
Because Blade is included out of the box and requires no external tooling such as Vite / MIx. Blade can be used immediately after installing a fresh version of Laravel. If you're familiar with vanilla JavaScript or another front end framework such as Vue or React, use that instead.
In my opinion having a "Laravel From Scratch" tutorial cover front frameworks and tooling would just complicate things. I have to work with far too many applications that use frontend frameworks where a simple blade template would do the job perfectly.
Why does the course "Laravel from scratch" spend so much time using Blade instead of pairing it with some front-end framework?
Which framework? The second you add a front-end framework to a beginner Laravel series, you drastically raise the prerequisite bar. Now, the viewer ALSO has to know JavaScript tooling, the frontend framework I pick, and potentially bundling.
IMO, Laravel and frontend framework communication should happen as part of a different, higher level series.
@JeffreyWay excatly
@JeffreyWay Thank you for your answer.
My question was more related to the unique advantages of Blade in certain scenarios compared to using Laravel purely as a backend. For someone who knows PHP and some front-end framework, I was just wondering, is there any benefit to learning how Blade functions?
@amil_murselovic because it allows you to build complete solutions without the added complexity of a front-end JS framework and API infrastructure
Please or to participate in this conversation.