Dude, this video was recomended to me a few months ago. You planted a seed of uncertainty and my frustration was going up with every node.js issue I had. And today after 4 years of JS development I am installing Laravel.
Great video!!! Laravel has a great performance too. I really don't like Next.js to big projects because it is not. Laravel is a great framework with a great community better than Next.js
Authentication is a fundamental feature that is so crucial to many applications, especially considering that other popular frameworks like Laravel and Rails have first-party authentication solutions, it seems only logical that JavaScript would follow suit.
What people fail to understand is that the purpose of server components is not solving a problem but creating a new market. NextJS fullstack is there to build small, quick cash grab SaaS. NextJS will become the new wordpress, difference is 15 years ago people made blogs, now they make SaaS.
Except its not good at small SaaS because even small SaaS apps need auth, multi-tenency and a bunch of features (queues, MFA etc) that come standard with laravel. There is almost nothing small enough that next.js as a full stack framework is a better option.
I didn't delve deeply into the fundamental skills of the old page router, but I invested so much time developing with it that I felt confident in my mastery of it. However, with the introduction of the App router, which operates in a completely different way, I don't feel motivated to start from scratch again. That being said, when I do encounter obstacles, I've found that good documentation is essential for a seamless developer experience. Thankfully, Laravel excels in this regard, providing excellent documentation that helps me navigate any challenges I may face.
@@bursteri The App router came out long enough ago, and it's been in beta, to understand how it works. Moreover, it has gotten simpler rather than more complex. So I don't quite understand your motivation. Maybe if you are a junior developer who is just entering the profession and regretting the wasted time - then yes, in development, at least in the js and web ecosystem we have quite dynamic changes, so either you get used to it, or there are more conservative areas of development where things don't change for years
I must respectfully disagree. In my opinion, time is our most valuable asset, and speed is paramount in business. In fact, my recent experience with App Router on my last project has shown me that incorporating server components into a primarily frontend framework does not make it simpler.
Dude, this video was recomended to me a few months ago. You planted a seed of uncertainty and my frustration was going up with every node.js issue I had. And today after 4 years of JS development I am installing Laravel.
Laravel embraces JS, so its not about about abandoning anything. Just making the best of both worlds!
Good content like always! Keep making more videos! :)
Thanks! Will do!
Great video!!!
Laravel has a great performance too. I really don't like Next.js to big projects because it is not. Laravel is a great framework with a great community better than Next.js
Thanks! Laravel is no slouch when it comes to performance 😎
I use Lucia auth with next js it's simple and come with greater dx
hi i don't know laravel but i use nestjs(backend) and Angular(frontend). and the DX is so awesome out of the box!
Great choice, Separating backend and front is the way to go.
Nest is basic angular on the backend
Nest is angular but its not basic 😂@@guled669
if auth was easy clerck would not exist. of course auth is hard and it's a roadblock when starting a project.
Authentication is a fundamental feature that is so crucial to many applications, especially considering that other popular frameworks like Laravel and Rails have first-party authentication solutions, it seems only logical that JavaScript would follow suit.
A question why not to use livewire instead of nextjs because will increase even more development speed and you are use just laravel ??
Livewire is very minimal Javascript like JQuery, mostly adopted by heavy backend developers
What people fail to understand is that the purpose of server components is not solving a problem but creating a new market. NextJS fullstack is there to build small, quick cash grab SaaS. NextJS will become the new wordpress, difference is 15 years ago people made blogs, now they make SaaS.
Can't argue with that - Next.js is indeed better-suited for creating smaller applications.
Except its not good at small SaaS because even small SaaS apps need auth, multi-tenency and a bunch of features (queues, MFA etc) that come standard with laravel. There is almost nothing small enough that next.js as a full stack framework is a better option.
@@kaf83 Ah I never said it was good, I said it was the target audience.
The problem in my opinion with next js is that you break maintainability.
Yes agree, I spent so much time learning the old Page router, now I'm just confused with client and server components
@@bursteri Could you share what you took so long to learn in the page router? And how often do you have to deal with knowledge obsolescence?
I didn't delve deeply into the fundamental skills of the old page router, but I invested so much time developing with it that I felt confident in my mastery of it. However, with the introduction of the App router, which operates in a completely different way, I don't feel motivated to start from scratch again.
That being said, when I do encounter obstacles, I've found that good documentation is essential for a seamless developer experience. Thankfully, Laravel excels in this regard, providing excellent documentation that helps me navigate any challenges I may face.
@@bursteri The App router came out long enough ago, and it's been in beta, to understand how it works. Moreover, it has gotten simpler rather than more complex. So I don't quite understand your motivation. Maybe if you are a junior developer who is just entering the profession and regretting the wasted time - then yes, in development, at least in the js and web ecosystem we have quite dynamic changes, so either you get used to it, or there are more conservative areas of development where things don't change for years
I must respectfully disagree. In my opinion, time is our most valuable asset, and speed is paramount in business. In fact, my recent experience with App Router on my last project has shown me that incorporating server components into a primarily frontend framework does not make it simpler.