yeah, F this sh*t honestly... I'll have to quit Next.js at some point except if they finally introduce a LTS version... I have a life outside of Next.js tutorials and docs...
I honestly agree and I haven't even used nextjs The fact that caching was automatic in v14 baffles the F out of me, like caching should always be opt-in
I am going to stick with Next.js 25. Life in the future is good. If you have any questions about what is coming next, please let me know, and I will share.
Hi Max, thanks for the video. Could you add a lecture to this course on how to make next.js app embeddable as a widget? Like, it can be usable by adding to any website.
I upgraded my portfolio from v14 to v15 and boom a component that was imported using next/dymanic function caused an error that said this function can't be used in server components even though it worked perfectly fine in v14. Tried a lot of solutions but didn't work and wasted 15min of my life for nothing and I just downgraded to v14. Really I regret using this framework and web development in general.
I bought the course you created using Next JS 14, and whenever you send a request in useFormState (now useActionState) using server actions it used to retain the user inputs, but now with Next JS 15, it no longer retain the user input, which I have no idea how to fix
Hi Max, thanks for the video. I have a question about working with the Next.js App Router for frontend-only projects. Does it make any difference? I'm using it in an intermediate-level project, and it's really frustrating because there isn't enough learning material for my team. On the other hand, I've used the Pages Router on another large project, and that was much easier. What are your thoughts on this?
However, based on my experience, using the Next.js App Router is a wise decision for a full-stack project but not for a frontend-only projects where your backend is running on another server
I always use the app router, I think it's much easier. Sure, very often you have to use "use client", but when you compose your components in the correct way it's really not an issue imo
It depends on a lot of things. 1) Where are you going to deploy your application. Custom server? Cloud server? 2) Type of application. Single Page? Multiple Page? 3) Do you need SEO? If you're building a simple SPA, I would choose React/React-Router, specially if you're deploying in a custom server.
do you have any course of nextjs like you did with flutter , we learnt flutter with you even we never coded before , do you have something like with nextjs , like teaching nextjs in sametime with js and html and css
@@johnsimms9444 Much simpler architecture, no idiotic abstraction like next.js, blazingly faster dev server with vite, not too serverly oriented just a right amount of server rendering unlike next js which lets you to literally do any server endpoint in the app, and a lot more. Just try it by yourself
Am I not seeing it, or is there a way in the config file to set cache for all of nextjs back to the previous Next 14 default? I don't want to set it per route/fetch, I liked the heavy-handed caching on one of my projects where I never ran into any issues with it.
@@HokagePain07 On enterprise apps I won't be until we understand it more. But there are some nice features worth upgrading, since 14 was mostly nothing anyway, and I have personal projects that I could upgrade without harm.
Honestly, I don't understand who uses this garbage... I retired next.js 2 already... except for a simplistic website that is still built on it... Their advertising was really strong but in practice it's just piles of garbage.. The development experience is also slow and impossible Instill really complex things... and we won't talk about the weird magics
Does it fix Next 14? In short, no. In long, noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo...
It's time to learn Next.js, AGAIN, for the fifth time this year! My god...
I feel so much for any real company which use this framework, for anyone using it to make "Pokedex" app is fine
yeah, F this sh*t honestly... I'll have to quit Next.js at some point except if they finally introduce a LTS version... I have a life outside of Next.js tutorials and docs...
I honestly agree and I haven't even used nextjs
The fact that caching was automatic in v14 baffles the F out of me, like caching should always be opt-in
This is so real. I’m seriously looking longingly at remix right now.
Odd they didn't wait til nextjs conf. Wonder if we get nextjs 16 coming in 2 days
I can't believe this framework (along with React) is so popular... the whole ecosystem is becoming one huge mess.
Exactly. I will never touch this abomination
This is a great overview of the key features and improvements in Next.js 15. Impressive focus on performance and developer experience.
I am going to stick with Next.js 25. Life in the future is good. If you have any questions about what is coming next, please let me know, and I will share.
Damn, can you tell me how to fetch data in NextJS 25 ?
Hi I will be having a problem with authentication in Next 24 how would Next 25 fix that issue
@@mahmoudfarghly2970 Next.js 25 uses telepathy to fetch data from users.
is my penis still small in the future?
Ok but will Next 26 fix Next 25?
'cache' for developers, 'cash' for vercel
LMAO good one
Thanks much, buddy
Next version of next is next month
The amazing thing about your comment is that it’s true every month, infinitely. It’s almost as if your comment has been cached automatically.
Ohhhhh!! Thats why they named it Next 🤯
I won't learn anything about nextjs15 until I know when nextjs16 will be release
great move 😅
Phew, yes, "Thankfully", I am in the middle of learning Next.js, and good thing they didn't add much
I worked with next JS and it was cool . I’m just addicted to PHP 😊
didnt knew you had a nextjs course. Got 1. tnx
Hi Max, thanks for the video. Could you add a lecture to this course on how to make next.js app embeddable as a widget? Like, it can be usable by adding to any website.
Next.js 15 course, the contents are all Nextjs 14
Thank you Max but it’s overwhelming!
I've tried to update yesterday and guess what: It breaks everything and I can rewrite my app. Awesome!
I upgraded my portfolio from v14 to v15 and boom a component that was imported using next/dymanic function caused an error that said this function can't be used in server components even though it worked perfectly fine in v14. Tried a lot of solutions but didn't work and wasted 15min of my life for nothing and I just downgraded to v14.
Really I regret using this framework and web development in general.
I bought the course you created using Next JS 14, and whenever you send a request in useFormState (now useActionState) using server actions it used to retain the user inputs, but now with Next JS 15, it no longer retain the user input, which I have no idea how to fix
Hi Max, please do a solidstart course
Hi Max, thanks for the video.
I have a question about working with the Next.js App Router for frontend-only projects. Does it make any difference? I'm using it in an intermediate-level project, and it's really frustrating because there isn't enough learning material for my team. On the other hand, I've used the Pages Router on another large project, and that was much easier.
What are your thoughts on this?
However, based on my experience, using the Next.js App Router is a wise decision for a full-stack project but not for a frontend-only projects where your backend is running on another server
I always use the app router, I think it's much easier. Sure, very often you have to use "use client", but when you compose your components in the correct way it's really not an issue imo
@@paw565 hi man thanks for you comment. Is there any way we connect so that we can share 💡?
It depends on a lot of things.
1) Where are you going to deploy your application. Custom server? Cloud server?
2) Type of application. Single Page? Multiple Page?
3) Do you need SEO?
If you're building a simple SPA, I would choose React/React-Router, specially if you're deploying in a custom server.
@@stacked-dev it sounds like a scam honestly lmao
do you have any course of nextjs like you did with flutter , we learnt flutter with you even we never coded before , do you have something like with nextjs , like teaching nextjs in sametime with js and html and css
Is there any section fpr next js 15 on your next js course? Because you already updated your title to next js 15?
You already updated your course title
yeah thats scam 😂😂
@@AbdurrahmanASUR 😂
Yeah it is just to lure more students to buy his course 😅
@@pixel-and-codeand they will found out most companies still uses React 15 with class components and Redux haha
Hi Max
Can you create a course on react micro frontend architecture
with not much changes in this version. it should be 14.1 or 14.2. Rather it should be 13.1 13.2 13.3.
Can u make state management video for nextjs in current course on udemy
Friendly tip: Don’t render on the server if you don’t need it (e.g., SEO, authentication). If needed, use Remix.
Why Remix? Why not nextjs?
Lmfao
@@johnsimms9444 Much simpler architecture, no idiotic abstraction like next.js, blazingly faster dev server with vite, not too serverly oriented just a right amount of server rendering unlike next js which lets you to literally do any server endpoint in the app, and a lot more. Just try it by yourself
I'm waiting for NextJs 18. These are still underage 😂
All my homies hate next js
why. i get this from many react users already.
@@hollycow8171 You have to build a real production app to realize how sh1t next.js is
im still learning the nextjs13 when thr nextjs14 and nextjs15 come out? i quit
My team is currently migrating every new project out of next.js, no intention to go back whatsoever
Migrating to what?
does nextjs with pages routing cache the fetch request by default ??
Next 15 installs React 19 rc.. which gives errors when downloading packages like framer-motion.. is there any fix or should i go with Next 14 for now?
Nah I'm sticking to Angular. I don't want my app breaking with each update.
Es difficult change the projwct of my job of next 13 to next 15?
Now, nextjs15 is hot, 3 days later nextjs 16 is out
Am I not seeing it, or is there a way in the config file to set cache for all of nextjs back to the previous Next 14 default? I don't want to set it per route/fetch, I liked the heavy-handed caching on one of my projects where I never ran into any issues with it.
So just do not upgrade it?
@@HokagePain07 On enterprise apps I won't be until we understand it more. But there are some nice features worth upgrading, since 14 was mostly nothing anyway, and I have personal projects that I could upgrade without harm.
man this is making me tired. Considering moving to React + Vite or SvelteKit
If this is tiresome for you, I advice to not go for React 18/19 + vitejs on big projects neither.
@@ben53933 Explain?
I first have to overcome the fear that I can understand React and actually use it
I will forever have a burning hatred for Vercel, I have no trust in them.
does anyone have nextjs 15 and deno2 boilerpate
Thank god im not on nextjs anymore
Yep, the best feeling about NextJS is "I don't care".
What did you replace Nextjs with?
@@mivandi3059 Nuxtjs . Was easier than expected.
Honestly, I don't understand who uses this garbage... I retired next.js 2 already... except for a simplistic website that is still built on it... Their advertising was really strong but in practice it's just piles of garbage.. The development experience is also slow and impossible Instill really complex things... and we won't talk about the weird magics
No
Remix
عالی بود
Next is using next version of next.js, not previous but next Next.
Does it fix Next 14? In short, no. In long, noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo...