There's a large community that uses dedicated backend frameworks (eg. Go, Laravel, Python) with SPA frontends. That won't be changing any time soon - these backend languages are waaaay more powerful than JS meta frameworks on the server side. I think your point makes sense for JS-only developers and certain kinds of apps. But there are plenty of apps that require the horsepower of a proper backend framework combined with the UX of an admin SPA.
@maximilian-schwarzmueller7 ай бұрын
Absolutely!
@hundop48264 ай бұрын
Happy to see you making more videos. I've taken your classes for some time.
@mohammadz54747 ай бұрын
Thank you Max for sharing your great advices , I needed this video , I really enjoy your videos and learn a lot from them
@ScottSchwartz-Owen5 ай бұрын
Max, love your explanations so much! Bravo!
@waynecheah2 ай бұрын
Latest developer survey clearly see all meta framework going down trend except Astro
@sudhansusatyam58357 ай бұрын
The metaframework is fine when we have javascript or nodejs as backend but what if we have other choice like java,go,python or php?
@techniquejoseph7 ай бұрын
Thanks Max, for a thoughtful take on a complex topic.
@mihaidornescu50147 ай бұрын
I am curious if in the future you will also offer a php course, maybe even Laravel?
@zaabimahdi7 ай бұрын
Next.js is good for static websites (e-commerce, marketing website) ... For web apps, where a lot of javascript is involved, still pure react the best option.
@rezapaledream84266 ай бұрын
Hello Max i just bought your next js toturial, but i dont know what should i do after app router part that you added recently. Should i skip page router and continue? Because i want use app router in my applications Or i need page router? Since you are using that for the rest of toturial. I am confused, would you please help me with that. I apprituate your consideration.
@THEROOT11117 ай бұрын
As always, very well said.
@hamzaswed7 ай бұрын
Thank you for sharing such valuable advices, keep up the fantastic work ✨✨
@hichembouallegue7 ай бұрын
Can Next.js handle very large real-world applications as a full stack? 🤔 I have reservations; it might be more suitable for frontend work, considering my current preference for a distributed backend approach using Nest.js.
@maskman48217 ай бұрын
Great talk ❤
@benjamincederholm44897 ай бұрын
Do you think this movement is challanging .NET Core as backend/api framework? Today a very common enterprise applications setup is to have react or angular as SPA served by .NET Core in the backend.
@o_glethorpe7 ай бұрын
Nextjs is only good if you are not the one paying the bills.
@misterfister35697 ай бұрын
So hard to listen to his speech...
@UwU-dx5hu6 ай бұрын
Why tho
@ozgurNY7 ай бұрын
I disagree
@maximilian-schwarzmueller7 ай бұрын
Would love to hear more details
@ozgurNY7 ай бұрын
@@maximilian-schwarzmueller I respectfully disagree with your perspective on Next.js, Remix, and similar frameworks as the future of web development. Allow me to illustrate my viewpoint with a concise example: Suppose my website attracts 100 daily visitors. These frameworks offer server-side rendering and SEO capabilities, but relying on platforms like Vercel can lead to significant monthly expenses, perhaps around $100. While this might be feasible for smaller websites, what happens when the traffic scales to 1,000 or even 1,000,000 clients per day? Would it be more efficient to render the website on the client's device rather than on Vercel's servers? While the former option is cost-free, the latter could accrue substantial expenses over time.
@xxXAsuraXxx7 ай бұрын
I have a feeling that JQuery might be returning as a King of web development