Having different caching behavior for dev vs production is legit psychotic. I have never had as frustrating an experience learning to use a new tool as I did with Next.js. It's like you are destined to run into esoteric problems either caused by shitty, unclear documentation or a total lack of documentation. Unless, of course, you get lucky with your google searching and find the answer on some github issue from a year ago.
i had a production problem in next, which i never had with react or angular ect. The compiler could not tell the different between my server and client file and it wanted me to overwrite my server file with 'use client'. So spend 2 hours and found DynamicHeader solution, silly LOL
Yep, although I'm starting to get worried about vanilla React as well. The latest release with server actions has me worried a bit. I prefer to have Client and Server strictly separated.
You definitely are one of the people who understand how Nextjs caching mechanisms work. Your explanation is waaay better than that of the vercel team, hands down! I struggled a lot trying to remove all of the caching on version 14. Awesome channel!
Hi Kyle, I think you nailed it in this video. After 25 yrs of programming I never got the built-in caching strategy of Next. It is also best practice in virtually all environments to cache purely for optimization reasons and never as default bevavior. Hope the Next.js team reconsiders and requires opt-in for *all* types of caching in RC 15.
Honestly, I've just stopped using next a while ago, been working with angular in my day job and now I'm just using it for all of my side projects as well. So much more enjoyable to code and no need to deal with all that mess next.js provides
@@null_spacex just because you hate it doesn’t mean it’s bad. Once you get the hang of it, it becomes really enjoyable to work with it. All these jr. devs are jumping in on what’s popular these days and hate what people love to hate without even trying out the tools. That’s a sad reality front-end development has been in for a while now.
I agree this is confusing, but the example is contrived, if your doing crud then you will need to invalidate the path which will be obvious when your working with it, also if you need specific catch scenarios your going to think about these, but agreed this will catch out some developers. Keep up the good work man
I went to set up a project yesterday and asked for the y on tailwind, it produced not config or post css and when I installed afterwards it still wouldn’t connect. Almost given up using next because it’s constant issues on build
I've ran into the same issues as I'm currently working on a frontend application that was connected to a headless CMS. I have a blog page where everything was working fine in development, as I added a new blog, it was being displayed in my frontend, but as soon as I pushed it live, that was no longer the case. The way I fixed it ( and I'm not entirely sure it's a good idea) is setting revalidate:0 on my fetch function. Is this a good practice?
As a react developer wanting to learn NextJS, this problem with 14 made me scrap the whole thing and switch back to regular react in my latest project. Might try again with NextJS 15 now that I understand the behavior from your video!
Exactly😂🤦♂️if there are any react developer is reading this, at first i was so hesitant to try out vue 3 and thought nothing can beat react, now it has been more than 3 years and i havent used nothing but vue/nuxt for all my work/side rpojects, this has been the best decision i have made and i encourage you to do so, i mean at this point its for your own benefits tbh
fucking front end is a mess. So glad I rarely develop in React, and mostly work on the backend outside of metaframeworks and focused on DICOM. In this role I now manage to completely avoid this shitshow, I honestly feel bad for you guys for having to suck this up. I miss when the debate was as simple as being about lifecycle methods and whatnot. This is wild.
@@ParwinderSingh-te7lb One of the worst decisions in life is to get into front end dev right now. I wonder how people are keeping up with all the frequent updates.
I have actually moved away from Nextjs because of these reasons. But in v15, do we need to ”force-dynamic” on the route to make the new fetch to work as expected - or can we just use useNoStore at fetch function level to make the route not staticly rendered?
Front end in general is OK. Just don't lock to the shitty hypie technologies to get to the point when they go even shittier. It was a lot of signals about this situation before on NextJS.
I'm old... I am still stuck with php for my personal page. It works like it did 20 years ago. Almost the same code, but now on php 8. For professional work, fortunately, I do not have to do web stuff very often. But that looks so f-ed up. Is this really state of the art? I thought writing cgis with perl was terrible. But that is even worse. Where is the benefit from that? What is the advantage? It all looks so crappy.
Thanks for this excellent video. Is the v15 doc already available? Our projects are heavily cached-based so we MUST trace every renders and every call and choose what to do with every single piece of sw
Hey Kyle 👋, I've been watching your content for 2 years now, I have learned so many things about web development from you, can you please make videos on projects, I think learning things is important but it is of no use if you don't apply it, so please make videos on project
videos on projects won't help find something your passionate about and jump into it. try coding for month staright and see what happens! will you get stuck, will you get even more motivated after a month, who knows... just do it and find out!
@macctosh I've done coding for 6 months now, and I feel the urge to build cool projects with the things I've learned, but I don't seem to find any interesting projects here on CZcams🤷♂️
Can you check whether the same behavior works if you pass the evaluated number to a variable instead of calling it directly? e.g. const num = Math.random {num} I'm wondering whether the `Object.is` comparison is messing with the caching somehow...directly returning an invoked function inside JSX isn't good practice, so if it only happens in this instance I think that's acceptable behavior.
I'm one of the few people that actually don't mind having pages static by default. I just hope they added easier ways to determine whether a page is static or not.
Next week's updates: Launching Next.js 16 fixing another something about caching and forgetting about a broken v14 and v15. Honestly, I have been struggling so much with weird issues in Next.js and unable to move fast in developing one of my side projects that's not even complex. I tried hard to do it in Next.js because the React team is pushing it towards it and I am comfortable writing React code. But I am starting to think of either moving to another framework like Remix or Nuxt or go React + Vite route.
@@marcuss.abildskov7175 Hi thanks for your reply. Are you personally using Remix? What are your thoughts on after a horrible experience with Next? Is it more stable and will it remain stable and up o date in the upcoming days as yo u know React 19 is coming and React Team and Next team are working together but Remix is not involved in that sense.
Same, stopped using Next after using it for 2 years a couple months ago because I got so tired of debugging the framework. Remix is in my opinion so much simpler and more enjoyable to use. Also vite for the dev server and build tool is a lot nicer and speeds up CI/CD and development by more than I expected it to. Next dev server and build process is atrociously slow for large projects.
I don't know if this kind of tutorial already exists from you, but im very interestet in building a simple next.js app but with a express backend - How to create, connect, send cookies to the Client, and all that stuff. :D Your Tutorails help me a lot to improve my skills :D
@@wielomarian the last time I tried to re-evaluate that combo (recently), which at this point I'd prefer over all the others, I got a bunch of issue with language server in vs code, and that sucks. DX is important and hope they'll provide some sort of improvements. It's seems unreal that their vscode extension, officially recommended on vuejs site is so bad. Or am I missing something?
I tried nextjs once, I don't get the attraction. Admittedly it was someone else's code, something from Edgedb, but the performance sucked and the dev folder was close to 1gb. A simple tiny no-framework node app blew it out of the water for some reason. Query response times dropped by about 30ms without next.
I think the practical strategy for using NextJS is like buying an iPhone. If the newest iPhone is a 10 and you want a new phone, buy the 9 because it's cheaper and almost just as good. In this case... maybe it's best to stick to NextJS 13. Seems like 14 and 15 aren't mature enough, and 15 is basically v14-2.0.
Great video. I don not use next.js. But it is a common phenomenon in recent years that new stuff comes up that is supposed to make your life easier but effectively it lowers productivity, stability and maintainability. Examples: hot reload in VS. Rarely ever works. Often leads into debugging not your real code but some old code. Python is another great example. We will all suffer in the future maintaining Millions of lines of code written in Python without any type safety and HORRIBLE coding practices.
I wish vue (nuxt) or remix had as big community as next js. Then I’d switch to nuxt or remix immediately. But let’s be honest: no matter how much madness comes in next js we will stil use it. Because good luck finding good libs for mid size + projects if you are using svelte or smth like that…
I agree that this is less than ideal. However, this seems to be very much an issue that can be addressed in future releases and should not taint the overall rating of the framework drastically.
Hey 1st comment. Caching is their kryptonite. Never learnt nextjs .. remix I have set my eyes on or astro. But to be real I am tired of these things alltogether. Need a break 😭
What really suck is that if you want to send notifications from next(server side) to a client, YOU NEED TO PAY for a service like pusher or code a node server, this part of serverless really suck... and they never mention this. So for big apps you still need Node 💁
@@pablom8854 ah i see. Well, they shouldn't have to mention that you need a server for something like that. What you're talking about either needs websockets or cron jobs or both, and a serverless environment never excels at those. And you don't necessarily need node/common server, but you will at least need a rabbitmq server in the end, so yeah, there is always a server involved.
@@thecoolnewsguy Oh yeah the "skill issue guy". Tell it to DHH. Now people love to code masturbate just to feel good about themselves. Skill issue is if you can't code without type hint, though it's a convenient feature but not if I have to scaffold it, ide should. I'd say improve your core and enjoy the experience of dynamic typing. You want static typed? Why use fake one, build with c# and stop polluting js.
Hi Kyle, I am a Next.js developer, and I was just wondering why you use a GET request if you know your data will be dynamic. Isn't the GET request supposed to be cached by the browser unless you specify cache-related headers?
I don't think a GET request is suitable for something so dynamic and crucial to remain dynamic. Perhaps a POST request is more appropriate in this context because it clearly indicates that the endpoint performs an operation that can yield different results each time it's called.
@@guanbo-yang It makes 100% sense to be a GET, as it is for retrieving data without any modifications, even if this data is dynamic, for example you want to retrieve user's information, this is going to be a GET and it is dynamic, as each user would have a different data set based on the token (user identifier) sent fron client. Caching a GET makes sense, but in the end it's not a general rule, some things you might not want to cache, it really depends on each specific situation. You should check the REST API verb conventions and see what's the meaning of them as these are some good standards put in place for quite a long time.
Skill issue Your fetch() single static url and with no options. In real world apps, if a fetch is truly dynamic, you'd pass it different GET/POST params and/or with auth headers. Does that not make Next 15 page opt for dynamic instead of static then? If yes then yes I agree it's a bug. If not, your RNG api being dynamic s contrived and not a thing to whine about when this fetch() I do expect to return static data and thus no need for the page to be dynamic.
Remix is superior. Nextjs defaults are still retarded and broken. Static page generation should obviously be opt-in, not forcing people to dig around in docs for hours to debug what's going on.
Next.js is becoming the new Java. Used by enterprises, not something many would choose for personal stuff. And, of course: Write once, debug everywhere.
Check Out Daily.dev: daily.dev/w/web-dev-simplified
Having different caching behavior for dev vs production is legit psychotic. I have never had as frustrating an experience learning to use a new tool as I did with Next.js. It's like you are destined to run into esoteric problems either caused by shitty, unclear documentation or a total lack of documentation. Unless, of course, you get lucky with your google searching and find the answer on some github issue from a year ago.
i had a production problem in next, which i never had with react or angular ect. The compiler could not tell the different between my server and client file and it wanted me to overwrite my server file with 'use client'. So spend 2 hours and found DynamicHeader solution, silly LOL
The problem is not Next but React itself
Solid JS is the future
@@ChichaGadproblem is react getting into bed with Nextjs. React should stay away from the Nextjs team if it needs to stay relevant in 2 years.
@@ChichaGad Some say Svelte after its upgrade xD
@@jannickpedersen4620 Svelte is great as well. But I think you haven't heard about SolidStart version 1.0 released recently
Another reason for me to switch to react-router v7, man next.js is a bunch of temporary solutions and weird work around every new release
Yep, although I'm starting to get worried about vanilla React as well. The latest release with server actions has me worried a bit. I prefer to have Client and Server strictly separated.
@@BRBS360 Same here
Never been more grateful I went all in on remix/react router. I can’t imagine having to deal with all these shenanigans
React Router: The return of the King 👑⚛️
it's not even out yet
You definitely are one of the people who understand how Nextjs caching mechanisms work. Your explanation is waaay better than that of the vercel team, hands down! I struggled a lot trying to remove all of the caching on version 14.
Awesome channel!
Hi Kyle, I think you nailed it in this video. After 25 yrs of programming I never got the built-in caching strategy of Next. It is also best practice in virtually all environments to cache purely for optimization reasons and never as default bevavior. Hope the Next.js team reconsiders and requires opt-in for *all* types of caching in RC 15.
I have a lot of love for Vue SSR behind a Varnish cache. Simple to code in and simple setup.
Looking forward to the inevitable upcoming video on Next 15 caching strategies. :D
Thanks u kyle
I was facing this problem and I finally found the answer through your video 😊
God bless u man🎉
With next js Frontend development is becaming rocket science, I miss Nuxt 😢
Honestly, I've just stopped using next a while ago, been working with angular in my day job and now I'm just using it for all of my side projects as well. So much more enjoyable to code and no need to deal with all that mess next.js provides
Dude 🤢🤮
@@null_spacex just because you hate it doesn’t mean it’s bad. Once you get the hang of it, it becomes really enjoyable to work with it. All these jr. devs are jumping in on what’s popular these days and hate what people love to hate without even trying out the tools. That’s a sad reality front-end development has been in for a while now.
@@null_spacex just because you dislike it doesn't mean it's shit. Each to their own. Once you get the hang of it, everything is pretty straightforward
@@qwerty-or1yg I feel the same way about Next
What about back-end?
I agree this is confusing, but the example is contrived, if your doing crud then you will need to invalidate the path which will be obvious when your working with it, also if you need specific catch scenarios your going to think about these, but agreed this will catch out some developers. Keep up the good work man
I went to set up a project yesterday and asked for the y on tailwind, it produced not config or post css and when I installed afterwards it still wouldn’t connect. Almost given up using next because it’s constant issues on build
New version of NEXT JS basically means update yourself and climb a cliff and then expect most of the things to break .ie. jump of that cliff
🤣
Another amazing explanation. Thanks Kyle!
I've ran into the same issues as I'm currently working on a frontend application that was connected to a headless CMS. I have a blog page where everything was working fine in development, as I added a new blog, it was being displayed in my frontend, but as soon as I pushed it live, that was no longer the case. The way I fixed it ( and I'm not entirely sure it's a good idea) is setting revalidate:0 on my fetch function. Is this a good practice?
That's the way it gets fixed. What it simply means is that the page details are fetched newly whenever the page is opened.
Does the force dynamic work on the pages router?
As a react developer wanting to learn NextJS, this problem with 14 made me scrap the whole thing and switch back to regular react in my latest project. Might try again with NextJS 15 now that I understand the behavior from your video!
😂😂😂 I can relate
I'm going back to Nuxt and Vue. It's stable now. This relationship with react and next is too toxic now.
Exactly. Nextjs is an infection to React. The React guys should stay the hell away from the Vercel guys if they still need to be relevant in 2 years.
😂😂 my thoughts too, I came from nuxt/Vue to react because of the job market
@@kevinisaac4958 Bingo my brother! Vue + Nuxt is the way. So much better DX & performance compared to that shitty Next.js...
Exactly😂🤦♂️if there are any react developer is reading this, at first i was so hesitant to try out vue 3 and thought nothing can beat react, now it has been more than 3 years and i havent used nothing but vue/nuxt for all my work/side rpojects, this has been the best decision i have made and i encourage you to do so, i mean at this point its for your own benefits tbh
@@kevinisaac4958 if it is the problem then why aren't people moving to remix
this version 15 is insane ahahaha, love you Kyle
is this behavior also present in page router?
fucking front end is a mess. So glad I rarely develop in React, and mostly work on the backend outside of metaframeworks and focused on DICOM. In this role I now manage to completely avoid this shitshow, I honestly feel bad for you guys for having to suck this up.
I miss when the debate was as simple as being about lifecycle methods and whatnot. This is wild.
To top it up now so much job layoffs .kids have to learn all this shit on top of sht and still getting no jobs.. despicable
@@ParwinderSingh-te7lb yeah. something's not right here.
chaos is the word
Use Angular. Problem solved
@@ParwinderSingh-te7lb One of the worst decisions in life is to get into front end dev right now. I wonder how people are keeping up with all the frequent updates.
Can someone tell me what is the default revalidation time in next js 14 fetch request, if I don't assign any revalidation in it.
I have actually moved away from Nextjs because of these reasons. But in v15, do we need to ”force-dynamic” on the route to make the new fetch to work as expected - or can we just use useNoStore at fetch function level to make the route not staticly rendered?
Front end in general is OK. Just don't lock to the shitty hypie technologies to get to the point when they go even shittier. It was a lot of signals about this situation before on NextJS.
I'm old... I am still stuck with php for my personal page.
It works like it did 20 years ago. Almost the same code, but now on php 8.
For professional work, fortunately, I do not have to do web stuff very often.
But that looks so f-ed up. Is this really state of the art?
I thought writing cgis with perl was terrible. But that is even worse.
Where is the benefit from that? What is the advantage? It all looks so crappy.
Thanks for this excellent video. Is the v15 doc already available?
Our projects are heavily cached-based so we MUST trace every renders and every call and choose what to do with every single piece of sw
redux is not working with react 19 and nextjs 15 , can you make a video on it ?
Why are you using Redux in 2024?
@@marcuss.abildskov7175 because redux is great data flow manager, its not only global state container. What is alternative for redux today?
@@marcuss.abildskov7175what should he use then??
@@marcuss.abildskov7175What's the best alternative solution?
@@marcuss.abildskov7175redux toolkit is good though
What about using const revalidate...?
Could you create a video about Atlassian's new framework-agnostic, low-level dnd library called "pragmatic-drag-and-drop"?
I actually liked the default client-side router cache. It made navigation within the app very fast. But I guess you can't please everyone.
Was geht Bruder
@@Bilo_7 was geht bei dir
Hey Kyle 👋, I've been watching your content for 2 years now, I have learned so many things about web development from you, can you please make videos on projects, I think learning things is important but it is of no use if you don't apply it, so please make videos on project
videos on projects won't help find something your passionate about and jump into it. try coding for month staright and see what happens! will you get stuck, will you get even more motivated after a month, who knows... just do it and find out!
@macctosh I've done coding for 6 months now, and I feel the urge to build cool projects with the things I've learned, but I don't seem to find any interesting projects here on CZcams🤷♂️
Goddamn everyday I become a little closer to migrating my entire month-old project to vite React + React Router instead of this cesspool
Love the video. 🎉
We just started nextjs in monorepo. Is anything good in v15?
React 19, so react compiler
I suspect these behaviors might even be different depending on if you're using SSR vs SSG. I'd guess your project is configured as SSG?
Does anyone have repo with these test examples so I can play myself ?
Can you check whether the same behavior works if you pass the evaluated number to a variable instead of calling it directly? e.g. const num = Math.random {num}
I'm wondering whether the `Object.is` comparison is messing with the caching somehow...directly returning an invoked function inside JSX isn't good practice, so if it only happens in this instance I think that's acceptable behavior.
I'm one of the few people that actually don't mind having pages static by default. I just hope they added easier ways to determine whether a page is static or not.
Next week's updates: Launching Next.js 16 fixing another something about caching and forgetting about a broken v14 and v15. Honestly, I have been struggling so much with weird issues in Next.js and unable to move fast in developing one of my side projects that's not even complex. I tried hard to do it in Next.js because the React team is pushing it towards it and I am comfortable writing React code. But I am starting to think of either moving to another framework like Remix or Nuxt or go React + Vite route.
If you wanna stick with React I would definitely go the Remix/React Router way
@@marcuss.abildskov7175 Hi thanks for your reply. Are you personally using Remix? What are your thoughts on after a horrible experience with Next? Is it more stable and will it remain stable and up o date in the upcoming days as yo u know React 19 is coming and React Team and Next team are working together but Remix is not involved in that sense.
Switched to Remix life is much simpler now 😊
Good luck convincing your team
I am the team
@@nishantmogha7550 yeah but the point stands I want to learn remix but all I see is nextjs jobs
Same, stopped using Next after using it for 2 years a couple months ago because I got so tired of debugging the framework. Remix is in my opinion so much simpler and more enjoyable to use. Also vite for the dev server and build tool is a lot nicer and speeds up CI/CD and development by more than I expected it to. Next dev server and build process is atrociously slow for large projects.
Remix is dead now
Everyone is singing the praise of Next.JS 15. I am confused why they did not highlight these issues like you did.
I don't know if this kind of tutorial already exists from you, but im very interestet in building a simple next.js app but with a express backend - How to create, connect, send cookies to the Client, and all that stuff. :D
Your Tutorails help me a lot to improve my skills :D
why use next with node? just use vite
next is a fullstack framework tho. do you mean a simple react UI with express backend?
@@chris94kennedy Hi, he's just uses Next UI and Express Backend
@@hannesz6322 think you're confusing Next UI with nextjs, they're different
i’m recently thinking about switching framework. guys what should i pick vue or angular either just stay with next js
You can't go wrong with Vue + Nuxt.js bro!
@@wielomarian the last time I tried to re-evaluate that combo (recently), which at this point I'd prefer over all the others, I got a bunch of issue with language server in vs code, and that sucks. DX is important and hope they'll provide some sort of improvements. It's seems unreal that their vscode extension, officially recommended on vuejs site is so bad. Or am I missing something?
What is the name of your current browser??
I am using Arc in this video.
What browser are you using?
Arc
Should I just learn PHP at this point? I kinda want a predictable framework
I tried nextjs once, I don't get the attraction. Admittedly it was someone else's code, something from Edgedb, but the performance sucked and the dev folder was close to 1gb. A simple tiny no-framework node app blew it out of the water for some reason. Query response times dropped by about 30ms without next.
If it isn't already, caching should be set at the route level. Some routes operate just fine with caching and others do not.
Hi can you please make a course on React and NodeJs
I think the practical strategy for using NextJS is like buying an iPhone. If the newest iPhone is a 10 and you want a new phone, buy the 9 because it's cheaper and almost just as good. In this case... maybe it's best to stick to NextJS 13. Seems like 14 and 15 aren't mature enough, and 15 is basically v14-2.0.
I guess if you have the fetch request in a .ts file instead of writing it in the page.tsx, it will work dynamically without having to specify that.
Great video. I don not use next.js. But it is a common phenomenon in recent years that new stuff comes up that is supposed to make your life easier but effectively it lowers productivity, stability and maintainability. Examples: hot reload in VS. Rarely ever works. Often leads into debugging not your real code but some old code. Python is another great example. We will all suffer in the future maintaining Millions of lines of code written in Python without any type safety and HORRIBLE coding practices.
"You saved me just in time! I had been stuck on this problem for four days. Thank you so much!"🤩🤩🤩❤️
You could have learned a new framework like remix in 4 days
@@Adityacode yeah i could, but had no choice, except solving, have gone far with my project.
I guess you can force not to cache. The cache would work for some sites where we really need it
I must switch to astro or react-router v7
hey kyle love you and your work ❤❤❤
Happy Eidul Adha
Get marry with him
Time to hit the doc and real entire thing again
I wish vue (nuxt) or remix had as big community as next js. Then I’d switch to nuxt or remix immediately. But let’s be honest: no matter how much madness comes in next js we will stil use it. Because good luck finding good libs for mid size + projects if you are using svelte or smth like that…
I agree that this is less than ideal. However, this seems to be very much an issue that can be addressed in future releases and should not taint the overall rating of the framework drastically.
every version: we broke nextjs
Hey 1st comment. Caching is their kryptonite. Never learnt nextjs .. remix I have set my eyes on or astro. But to be real I am tired of these things alltogether. Need a break 😭
What really suck is that if you want to send notifications from next(server side) to a client, YOU NEED TO PAY for a service like pusher or code a node server, this part of serverless really suck... and they never mention this. So for big apps you still need Node 💁
NextJS 15 especially solved this, right?
What do you mean with "notifications"?
@@upsxace sending actions from the server to the client
@@pablom8854 ah i see. Well, they shouldn't have to mention that you need a server for something like that. What you're talking about either needs websockets or cron jobs or both, and a serverless environment never excels at those. And you don't necessarily need node/common server, but you will at least need a rabbitmq server in the end, so yeah, there is always a server involved.
Go Remix.
Reached its end of life now, focus is on React router
Better to use Pages in Next
This is a fucking mess I regret every time I use next.js every time there is something that just don't make any sense
Am using nextjs v12 and am not changing up anytime soon.
I thought they were doing away with the need for using force-dynamic in Next.js 15, seems not to be the case. Boggles the mind.
Yeah day by day it just pushes me more into HTMX + Ocaml stack
Next and Typescript are killing react 😴
TypeScript is improving it and people who say otherwise have skill issues as it's easy as well
@@thecoolnewsguy Oh yeah the "skill issue guy". Tell it to DHH. Now people love to code masturbate just to feel good about themselves. Skill issue is if you can't code without type hint, though it's a convenient feature but not if I have to scaffold it, ide should. I'd say improve your core and enjoy the experience of dynamic typing. You want static typed? Why use fake one, build with c# and stop polluting js.
I'm just waiting for Svelte 5. Once it become stable, I will never come back to the Next.js
it was already difficult learning nextjs .not again ...
Solid JS is the future
Hope Inertia will support Solid JS soon so we can have a sane front-end development and use Laravel to have a sane back-end development
@@luznoceda423 Hell yeah du-...
Wait what!? Laravel?
Hi Kyle, I am a Next.js developer, and I was just wondering why you use a GET request if you know your data will be dynamic. Isn't the GET request supposed to be cached by the browser unless you specify cache-related headers?
GET is for getting data w/o modifying it
How else would you GET your data?
I don't think a GET request is suitable for something so dynamic and crucial to remain dynamic. Perhaps a POST request is more appropriate in this context because it clearly indicates that the endpoint performs an operation that can yield different results each time it's called.
@@guanbo-yang It makes 100% sense to be a GET, as it is for retrieving data without any modifications, even if this data is dynamic, for example you want to retrieve user's information, this is going to be a GET and it is dynamic, as each user would have a different data set based on the token (user identifier) sent fron client. Caching a GET makes sense, but in the end it's not a general rule, some things you might not want to cache, it really depends on each specific situation.
You should check the REST API verb conventions and see what's the meaning of them as these are some good standards put in place for quite a long time.
@@guanbo-yang maybe you should read up on the different HTTP request methods and what their purpose are
nextjs 15 is not even released, this video might make u think it's released, why are you complaining about something that still in development?
Let me comment here From Namibia 🇳🇦
Me laughs in SvelteKit
Your voice is so deep 😍😍 I can't concentrate
What do you mean next 15??? 14 isnt even fully supported yet.........
I’m just gonna stick with Vite + Tanstack router for now
I honestly can't believe everyone isn't over NextJS yet. It started off good then rapidly went downhill.
Sadly its promoted by React itself. NextJS is just a bugy mess
people just need to stop using react
@@ellisj98 yeah, Im starting to look into Angular, but is not so easy when huge part of web FE runs on React,
@@ellisj98pays big bucks + it is easy for me
what do you recommend instead?
This feel like or looks like trolling, on njs end lol
You see why I'm still on next v 12
Is that safari 😆
Larval-inertia .. the old reliable
You could’ve highlighted the active links, don’t make it more frustrating.
Skill issue
Your fetch() single static url and with no options. In real world apps, if a fetch is truly dynamic, you'd pass it different GET/POST params and/or with auth headers. Does that not make Next 15 page opt for dynamic instead of static then?
If yes then yes I agree it's a bug. If not, your RNG api being dynamic s contrived and not a thing to whine about when this fetch() I do expect to return static data and thus no need for the page to be dynamic.
I’m still on v13
I switched to Remix. I don't like the way they do things.
Ever since I started hearing about NextJs there's always some issue or some update. Always. Ts a pass for me.
Remix is superior. Nextjs defaults are still retarded and broken. Static page generation should obviously be opt-in, not forcing people to dig around in docs for hours to debug what's going on.
i'm learning Astro
i just made a webapp and i'm still on Next 13 pages router, worry free
"Whatever happened to predictability..."
"JS & CSS... a little PHP!"
Why is everyone using theos browser 😤😤😤😤
You’re kidding right lol
@@null_spacex no seriously. Why🐸
@@null_spacexnope i’m wondering too
and I thought Nuxt bugs were bad. Haha haha.
A big F U to whoever wanted to play with developers using caching. Back to simple react.
Next.js is becoming the new Java. Used by enterprises, not something many would choose for personal stuff. And, of course: Write once, debug everywhere.
Java is robust and changes very little. So, post can be summed up as "Tell me you don't know squat about Java without telling me"
@@punsmith Oh yes, you're totally right. It was just a joke anyway. The only thing that doesn't change with Next.js are the cached responses 😉
Why waste time using Next.js when you have Frameworks like Nuxt and Sveltekit
Simply change fmk
First comment 😊
Gtfo
@@andreas_bergstromBut there's your mum out there.... Should I?? 💀
NPC
Hey need some work do you guys help me out