Check Out Daily.dev: daily.dev/w/web-dev-simplified
@incrypted607
3 ай бұрын
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.
@jannickpedersen4620
3 ай бұрын
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
@ChichaGad
3 ай бұрын
The problem is not Next but React itself Solid JS is the future
@kevinisaac4958
3 ай бұрын
@@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.
@jannickpedersen4620
3 ай бұрын
@@ChichaGad Some say Svelte after its upgrade xD
@ChichaGad
3 ай бұрын
@@jannickpedersen4620 Svelte is great as well. But I think you haven't heard about SolidStart version 1.0 released recently
@zelli840
2 ай бұрын
What we need in next js 15 caching wise: -no cache by default -not having to add "force-dynamic" -same behavior in dev vs production
@dcd_music
2 ай бұрын
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!
@luffythestrchykid
3 ай бұрын
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
@brainites
3 ай бұрын
🤣
@AK-ij4qf
3 ай бұрын
Goddamn everyday I become a little closer to migrating my entire month-old project to vite React + React Router instead of this cesspool
@nishantmogha7550
3 ай бұрын
Switched to Remix life is much simpler now 😊
@looming_
3 ай бұрын
Good luck convincing your team
@nishantmogha7550
3 ай бұрын
I am the team
@ParwinderSingh-te7lb
3 ай бұрын
@@nishantmogha7550 yeah but the point stands I want to learn remix but all I see is nextjs jobs
@xytric8245
3 ай бұрын
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.
@lazymass
3 ай бұрын
Remix is dead now
@jimmymac601
3 ай бұрын
If it isn't already, caching should be set at the route level. Some routes operate just fine with caching and others do not.
@nothingisreal6345
3 ай бұрын
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.
@realtebo
2 ай бұрын
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
@hannesz6322
3 ай бұрын
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
@pablom8854
3 ай бұрын
why use next with node? just use vite
@chris94kennedy
3 ай бұрын
next is a fullstack framework tho. do you mean a simple react UI with express backend?
@hannesz6322
3 ай бұрын
@@chris94kennedy Hi, he's just uses Next UI and Express Backend
@chris94kennedy
3 ай бұрын
@@hannesz6322 think you're confusing Next UI with nextjs, they're different
@AAfzal-lk2nf
3 ай бұрын
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
@hardcorecode
3 ай бұрын
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!
@AAfzal-lk2nf
3 ай бұрын
@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 KZitem🤷♂️
@Muphet
3 ай бұрын
every version: we broke nextjs
@chandrakanthchintada8029
3 ай бұрын
I guess you can force not to cache. The cache would work for some sites where we really need it
@ParwinderSingh-te7lb
3 ай бұрын
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 😭
@kaksarkar
3 ай бұрын
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
@namandeepnegi1709
2 ай бұрын
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.
@iPankBMW
3 ай бұрын
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?
@utkuonursahin1237
3 ай бұрын
I'm just waiting for Svelte 5. Once it become stable, I will never come back to the Next.js
@geelemo
2 ай бұрын
You see why I'm still on next v 12
@funfstuck
3 ай бұрын
i’m recently thinking about switching framework. guys what should i pick vue or angular either just stay with next js
@wielomarian
3 ай бұрын
You can't go wrong with Vue + Nuxt.js bro!
@paolo-e-basta
3 ай бұрын
@@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?
@nnokki
3 ай бұрын
Your voice is so deep 😍😍 I can't concentrate
@yashchauhan5710
12 күн бұрын
im using dynamic import in the page and its conflicting lmaoo
@lucascubile7141
3 ай бұрын
What do you mean next 15??? 14 isnt even fully supported yet.........
@m12652
3 ай бұрын
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.
@PraiseYeezus
3 ай бұрын
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.
@chambaderaphael8946
2 ай бұрын
Simply change fmk
@fungilation
2 ай бұрын
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.
@guanbo-yang
3 ай бұрын
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?
@lasse-mo
3 ай бұрын
GET is for getting data w/o modifying it
@hnccox
3 ай бұрын
How else would you GET your data?
@guanbo-yang
3 ай бұрын
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.
@schular94
3 ай бұрын
@@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.
@hnccox
3 ай бұрын
@@guanbo-yang maybe you should read up on the different HTTP request methods and what their purpose are
@Ivan-wm6gm
3 ай бұрын
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
@BRBS360
3 ай бұрын
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.
@aissa-dev1
3 ай бұрын
@@BRBS360 Same here
@malachiconstant2756
3 ай бұрын
Never been more grateful I went all in on remix/react router. I can’t imagine having to deal with all these shenanigans
@luznoceda423
3 ай бұрын
React Router: The return of the King 👑⚛️
@MrPogi-lf5gz
3 ай бұрын
it's not even out yet
@siya.abc123
3 ай бұрын
I'm going back to Nuxt and Vue. It's stable now. This relationship with react and next is too toxic now.
@kevinisaac4958
3 ай бұрын
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.
@georgemwaniki
3 ай бұрын
😂😂 my thoughts too, I came from nuxt/Vue to react because of the job market
@wielomarian
3 ай бұрын
@@kevinisaac4958 Bingo my brother! Vue + Nuxt is the way. So much better DX & performance compared to that shitty Next.js...
@_iyoub
3 ай бұрын
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
@AvikNayak_
3 ай бұрын
@@kevinisaac4958 if it is the problem then why aren't people moving to remix
@EinChris75
3 ай бұрын
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.
@0-Will-0
3 ай бұрын
I have a lot of love for Vue SSR behind a Varnish cache. Simple to code in and simple setup.
@TheMindfulCraftsman
2 ай бұрын
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.
@qwerty-or1yg
3 ай бұрын
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
3 ай бұрын
Dude 🤢🤮
@qwerty-or1yg
3 ай бұрын
@@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.
@qwerty-or1yg
3 ай бұрын
@@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
@null_spacex
3 ай бұрын
@@qwerty-or1yg I feel the same way about Next
@govindamishra3746
3 ай бұрын
What about back-end?
@codinginflow
3 ай бұрын
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.
@Bilo_7
3 ай бұрын
Was geht Bruder
@codinginflow
3 ай бұрын
@@Bilo_7 was geht bei dir
@TheOnceAndFutureDoug
3 ай бұрын
Looking forward to the inevitable upcoming video on Next 15 caching strategies. :D
@chris94kennedy
3 ай бұрын
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
3 ай бұрын
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
@chris94kennedy
3 ай бұрын
@@ParwinderSingh-te7lb yeah. something's not right here.
@chris94kennedy
3 ай бұрын
chaos is the word
@marcuss.abildskov7175
3 ай бұрын
Use Angular. Problem solved
@AvikNayak_
3 ай бұрын
@@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.
@georgemwaniki
3 ай бұрын
With next js Frontend development is becaming rocket science, I miss Nuxt 😢
@atimney
3 ай бұрын
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
@golden_smiles
3 ай бұрын
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.
@하경-e7z
3 ай бұрын
Thanks u kyle I was facing this problem and I finally found the answer through your video 😊 God bless u man🎉
@abacuz
Ай бұрын
one thing I don't understand with this reasoning, on a page that is going to just hafve static content, why would you even want it to render dynamically?
@eleah2665
3 ай бұрын
Go Remix.
@xxXAsuraXxx
3 ай бұрын
Reached its end of life now, focus is on React router
@thedailycutline278
3 ай бұрын
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?
@pyquix8576
3 ай бұрын
Next and Typescript are killing react 😴
@unknownguywholovespizza
2 ай бұрын
TypeScript is improving it and people who say otherwise have skill issues as it's easy as well
@pyquix8576
2 ай бұрын
@@unknownguywholovespizza 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.
@JM-st1le
12 күн бұрын
Typescript? How?
@CodeXBro
3 ай бұрын
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
3 ай бұрын
If you wanna stick with React I would definitely go the Remix/React Router way
@CodeXBro
3 ай бұрын
@@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.
@nanonkay5669
3 ай бұрын
Nah Next JS is becoming less and less viable. Too many breaking changes bruh, wtf? Time for another framework
@kashnigahbaruda
3 ай бұрын
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.
@DR-ee4wv
3 ай бұрын
I hate next.js...because of this I almost lost my client.. Guys if you want to take advice from me.. build your website with other tech..For me Astro is the king..you can use react you can use svelte..and performance is on fire for Astro... To my opinion and wordpress custom made theme is still most user and client friendly
@anhvuuc8693
3 ай бұрын
f* nextjs 😢 they make me so confused after update. i will change to qwik or astro because this
@codeinProjects3295
3 ай бұрын
redux is not working with react 19 and nextjs 15 , can you make a video on it ?
@marcuss.abildskov7175
3 ай бұрын
Why are you using Redux in 2024?
@Bazan-gd3lb
3 ай бұрын
@@marcuss.abildskov7175 because redux is great data flow manager, its not only global state container. What is alternative for redux today?
@kashmirtechtv2948
3 ай бұрын
@@marcuss.abildskov7175what should he use then??
@charleschukwuemeka8482
3 ай бұрын
@@marcuss.abildskov7175What's the best alternative solution?
@subhamsubian6677
2 ай бұрын
@@marcuss.abildskov7175redux toolkit is good though
@marcuss.abildskov7175
3 ай бұрын
How about using a proper framework instead of that React garbage? Web developers need to get a grip on reality.
@hvwong2044
Ай бұрын
yes, caching is confusing for me in next14
@Zagoorland
3 ай бұрын
Me laughs in SvelteKit
@Flash136
3 ай бұрын
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.
@ollienicholson
27 күн бұрын
appreciate the clip bro - keep up the good work
@fanush3754
3 ай бұрын
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?
@charleschukwuemeka8482
3 ай бұрын
That's the way it gets fixed. What it simply means is that the page details are fetched newly whenever the page is opened.
@felipefregginrules
3 ай бұрын
Does the force dynamic work on the pages router?
@sagart00100
3 ай бұрын
it was already difficult learning nextjs .not again ...
@hledaczvirat_cz
3 ай бұрын
Better to use Pages in Next
@wielomarian
3 ай бұрын
Next.js just fuckin SUCKS!!!! Constant errors,, stupid workarounds... It ain't shit compared to the DX offered by Vue.js + Nuxt or SolidJS.
@tuancao85
3 ай бұрын
Another amazing explanation. Thanks Kyle!
@Kostrytskyy
3 ай бұрын
Once again, why do we need Nextjs at this point? I do have 6+ years of experience with React, working mostly on internal or under auth apps. I do not need all this crap with SSR, SSG, SEO whatsoever. I don't particularly appreciate how we are getting heavily pushed towards things we don't actually need. Server components? What for? Just to render a component 1ms faster on a 5yo phone? And the React team getting in bed with Vercel is just ugly, and unethical.
@curiouslycory
2 ай бұрын
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?
@snivels
2 ай бұрын
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.
@alexandertarasenko3038
3 ай бұрын
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…
@frinno_io
2 ай бұрын
Ever since I started hearing about NextJs there's always some issue or some update. Always. Ts a pass for me.
@abidibnazam4462
3 ай бұрын
Why waste time using Next.js when you have Frameworks like Nuxt and Sveltekit
@engine_man
2 ай бұрын
I’m still on v13
@sean1334
3 ай бұрын
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!
@lucdina5118
2 ай бұрын
😂😂😂 I can relate
@Nscb1947
3 ай бұрын
A big F U to whoever wanted to play with developers using caching. Back to simple react.
@nikmat
3 ай бұрын
You could’ve highlighted the active links, don’t make it more frustrating.
@doppeltevier
3 ай бұрын
Could you create a video about Atlassian's new framework-agnostic, low-level dnd library called "pragmatic-drag-and-drop"?
@SukoonBeautifulMusic
3 ай бұрын
Everyone is singing the praise of Next.JS 15. I am confused why they did not highlight these issues like you did.
@justine_chang39
2 ай бұрын
i just made a webapp and i'm still on Next 13 pages router, worry free
@FrontendFanatic
3 ай бұрын
Should I just learn PHP at this point? I kinda want a predictable framework
@goncaloshred
3 ай бұрын
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.
@melvin4829
3 ай бұрын
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
@holgerflick
3 ай бұрын
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.
@krtirtho
3 ай бұрын
Yeah day by day it just pushes me more into HTMX + Ocaml stack
@monarchgam3r
3 ай бұрын
I’m just gonna stick with Vite + Tanstack router for now
@e_tas_
3 ай бұрын
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.
@huyifan83
3 ай бұрын
I switched to Remix. I don't like the way they do things.
@irom77
2 ай бұрын
Does anyone have repo with these test examples so I can play myself ?
@andrewwachira1
3 ай бұрын
Am using nextjs v12 and am not changing up anytime soon.
@charleschukwuemeka8482
3 ай бұрын
What about using const revalidate...?
@viewpoint8976
3 ай бұрын
Let me comment here From Namibia 🇳🇦
@fullstacklarry
3 ай бұрын
and I thought Nuxt bugs were bad. Haha haha.
@rationalindianguy
3 ай бұрын
Hi can you please make a course on React and NodeJs
@jellyfish1772
3 ай бұрын
Why is everyone using theos browser 😤😤😤😤
@null_spacex
3 ай бұрын
You’re kidding right lol
@jellyfish1772
3 ай бұрын
@@null_spacex no seriously. Why🐸
@funfstuck
3 ай бұрын
@@null_spacexnope i’m wondering too
@dj10schannel
3 ай бұрын
This feel like or looks like trolling, on njs end lol
@tajamalrafiq3651
3 ай бұрын
We just started nextjs in monorepo. Is anything good in v15?
@lazymass
3 ай бұрын
React 19, so react compiler
@umusilimu
3 ай бұрын
I must switch to astro or react-router v7
@MrPogi-lf5gz
3 ай бұрын
i'm learning Astro
@kasper369
3 ай бұрын
Time to hit the doc and real entire thing again
@oladejiraji2919
3 ай бұрын
Is that safari 😆
@jeffreyjdesir
3 ай бұрын
"Whatever happened to predictability..."
@jeffreyjdesir
3 ай бұрын
"JS & CSS... a little PHP!"
@pablom8854
3 ай бұрын
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 💁
@luzaw4957
3 ай бұрын
NextJS 15 especially solved this, right?
@upsxace
3 ай бұрын
What do you mean with "notifications"?
@pablom8854
3 ай бұрын
@@upsxace sending actions from the server to the client
@upsxace
3 ай бұрын
@@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.
Пікірлер: 245