🤣🤣🤣 I had to learn the traditional redux first, then move on to learning redux toolkit. Had severe headaches😂. He sounded not too optimistic about redux. Is there a replacement for it already
@@emenikedaniel I'm not sure about whether it scales. I can only guess it does. However, another alternative that I know of is mobx; which I know scales (Postman web app uses it).
Recoil and Zustand are both very nice, simple libraries for dealing with global state. I'm not sure how well they work in a larger project though. MobX might be worth checking out as well.
Frameworks first. (See his latest controversial tweet.) This solves the routing and data fetching problem, plus caches data globally without any effort from the developer. React has also been experimenting with caching all fetch requests and have created a "cache" function for any asynchronous calls like what would come from an SDK. Both are behind experimental flags. Both mean first class async support for React with global cache. (No need to wrap it in a useEffect.) For everything else, if Context isn't good enough for your app (it probably is), then there are better options. But in terms of what he's talking about, and what the entire React core team has been talking about since NextConf, is primarily frameworks.
i always hated Redux while i'm using in 2 projects. it feels just not the good way to do state management, boilerplates and concept that you need to explain to your team but you have no explanation why it should be like this. over engineering state management.
Love me some history of software engineering videos ❤
Solid and Qwik documentary would be really awesome in this perticular period of time.
Did you know that Flux was inspired by The Elm Architecture from Elm programming language?
That Cannondale in the background...😋
When the documentary will be released?
On the 10th of Feb! We'll have a live premiere at 7pm CET. 🔥
@@Honeypotio Cool its will be the release of the react documentaries also the Feb 10
@@heljhumenad that's the documentary they're talking about
a lot of request state management can be taken care of by react-query (now tanstack query)
Which can first though, useReducer or reduce? I just want to know the full story of the origins of that name.
Nice, Nice, Nice! About the reducers though, I know many clojurists that might not like his comments.
me who just started learning Redux: _ah shit_
😂
Redux --- or over engineered state management
Interesting!
What’s wrong with storing fetched data in redux?
🤣🤣🤣 I had to learn the traditional redux first, then move on to learning redux toolkit. Had severe headaches😂. He sounded not too optimistic about redux. Is there a replacement for it already
Zustand
@@Languagist For complex logic at enterprise level?🤔
@@emenikedaniel I'm not sure about whether it scales. I can only guess it does. However, another alternative that I know of is mobx; which I know scales (Postman web app uses it).
Hmmm... No word on Elm? 🤔
Better solutions? Like context?
i would love to know what he meant by: "better solutions"
I'd think less convoluted (or more "cleaner"?) ways of doing stuff, like data fetching which he pointed out.
Recoil and Zustand are both very nice, simple libraries for dealing with global state. I'm not sure how well they work in a larger project though. MobX might be worth checking out as well.
@@gkoymnbxykfb Are these better alternatives to Redux? MobX has been around for just as long...
sounds like react-query to me tbh
Frameworks first. (See his latest controversial tweet.) This solves the routing and data fetching problem, plus caches data globally without any effort from the developer. React has also been experimenting with caching all fetch requests and have created a "cache" function for any asynchronous calls like what would come from an SDK. Both are behind experimental flags. Both mean first class async support for React with global cache. (No need to wrap it in a useEffect.)
For everything else, if Context isn't good enough for your app (it probably is), then there are better options. But in terms of what he's talking about, and what the entire React core team has been talking about since NextConf, is primarily frameworks.
So this is the guy responsible for making front end so confusing. Well I guess he works at Meta so it makes sense.
😂😂😂😂
🤜🏻🤛🏻
Yeah, I got it. I heard "Don't use it anymore". 😉
i always hated Redux while i'm using in 2 projects. it feels just not the good way to do state management, boilerplates and concept that you need to explain to your team but you have no explanation why it should be like this. over engineering state management.
Zustand is best
first
second :)
😉
Redux is absolutely garbage