I really like how Zustand solve the state problem without creating more problems to deal with, at least in the simple apps. Btw what font do u use in vscode?
Think react query and form libs need to be mentioned because those are alternatives that help offload what people think of as “global” state and help organize slices of state.
I do not know about all the up to down approach libs… I clouds be wrong, but it always feels like a monolithic application. Too much thing in a single react component. Usually what I’m doing is to use JOTAI every time that I want the state to be shared among componentes and I create a custom hook to manipulate the data. This custom hook introduces all methods needed globally to manipulate data. It allows me to use things like SWR to controle the server state, for example.
For me, I don't think that recoil's atom cannot store function is a problem as we can export the function and give it the required fields. Maybe there's some use case that needs to store functions in a global state? I'm not sure, at least I don't encounter it yet
In recoil you can write selectors that take care of this, like a middleware between atoms and your components. Or am I missing something here, it's all quite new to me
You talk about how jotai is super simple, but I fear your excitement got the better of the demo. Clearly, you're passionate about it, but you went way too fast for someone who is trying to get an idea about how it works. Still a great talk. I'll have to skim over it for now and research myself which is fine but because you went too fast it just makes it feel way more complex.Oh god it gets even faster after that... I had to drop it... you killed my brain. I mean I've had a day of work, I'm tired, it would really help if you'd slow down.
Since Zustand and Jotai are both really light ... why not just use both of them ? So for quick useState-like stores, you use Jotai and for fully managed stores you use Zustand ? what do you guys think about it ?
I think you should just use one thing and be consistent throughout your app. Using two systems to do similar things like that is just adding complexity and unnecessary bloat; even if it is small.
useContext is good for state that doesn't change often like light/dark theme mode. useContext causes all components subscribed to it's values to re-render when a value changes. react-tracked can help improve performance of useContext but there are better solutions for frequently updated global state.
@@jii808i wish I would've come accross this comment 1 month earlier. I don't know why people/ content creators don't tell from start what's best practices. They would rather teach application of usecontext and leave at that. But they hardly tell when it should be used and what are its limitations and drawbacks. Surprisingly enough I found out yesterday what it does after I enabled highlight component on rerender option In react profiler
@@thorw2136 I don’t think most content creators know themselves. I’m using Zustand mostly for global state, react query for server state. Context rarely.
I wish typescript was t the standard in RUclips tutorials anymore. It's very confusing to see as I'm still trying to understand more complex JavaScript and advanced React stuff. So to through in typescript is a little bit much for me, personally. I feel like it's only really used in very public facing production environments too.
i checked, and i think zustand and easy peasy has similar implementation, for *creating a store* that is, except that with zustand there is no Provider
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
I really like how Zustand solve the state problem without creating more problems to deal with, at least in the simple apps. Btw what font do u use in vscode?
yep, it just do what it have to do
Jetbrains Mono
Jotai is more comfortable with me, save a lot bundle size, easy peasy management, and writing functional programming is wild
we dev simplified guy with a beard
There's also MobX which is still a valid alternative for state management.
What do you think about Valtio ? 🤔 do you already try it ?
I love Zustand - just wish you could separate state into slices like Redux. I understand that design a little better
if they are the same just use Redux, what's the point of learning Zustand
it can
you can do that
each createStore is a slice of its own, at least that's how i understand it
Think react query and form libs need to be mentioned because those are alternatives that help offload what people think of as “global” state and help organize slices of state.
I do not know about all the up to down approach libs… I clouds be wrong, but it always feels like a monolithic application. Too much thing in a single react component.
Usually what I’m doing is to use JOTAI every time that I want the state to be shared among componentes and I create a custom hook to manipulate the data. This custom hook introduces all methods needed globally to manipulate data. It allows me to use things like SWR to controle the server state, for example.
For me, I don't think that recoil's atom cannot store function is a problem as we can export the function and give it the required fields. Maybe there's some use case that needs to store functions in a global state? I'm not sure, at least I don't encounter it yet
In recoil you can write selectors that take care of this, like a middleware between atoms and your components. Or am I missing something here, it's all quite new to me
Why are you trying to make recoil to be like redux/zustland?
The ones I liked the most were rematch and recoil. Missing from the list to review Mobx
Zustand is german and means state
And jotai is Japanese and also means state.
And both are made by the same people ;)
i think zustand is easier, and i will vote for zustand
Base Redux users are masochist 😅
Siempre pense que redux era horrible, ahora por fin veo que hay mejores alternativas
You talk about how jotai is super simple, but I fear your excitement got the better of the demo. Clearly, you're passionate about it, but you went way too fast for someone who is trying to get an idea about how it works. Still a great talk. I'll have to skim over it for now and research myself which is fine but because you went too fast it just makes it feel way more complex.Oh god it gets even faster after that... I had to drop it... you killed my brain. I mean I've had a day of work, I'm tired, it would really help if you'd slow down.
don't some people just use React-query now as a state manager if all they need to do is share data from server to components.
Hold on, Redux Toolkit is a Redux alternative? 😮
Since Zustand and Jotai are both really light ... why not just use both of them ? So for quick useState-like stores, you use Jotai and for fully managed stores you use Zustand ? what do you guys think about it ?
I think you should just use one thing and be consistent throughout your app. Using two systems to do similar things like that is just adding complexity and unnecessary bloat; even if it is small.
Legend state prob didn’t exist but it’s api is also nice and clean
How about usecontext?
useContext is good for state that doesn't change often like light/dark theme mode. useContext causes all components subscribed to it's values to re-render when a value changes. react-tracked can help improve performance of useContext but there are better solutions for frequently updated global state.
@@jii808i wish I would've come accross this comment 1 month earlier.
I don't know why people/ content creators don't tell from start what's best practices.
They would rather teach application of usecontext and leave at that. But they hardly tell when it should be used and what are its limitations and drawbacks.
Surprisingly enough I found out yesterday what it does after I enabled highlight component on rerender option
In react profiler
@@thorw2136 I don’t think most content creators know themselves. I’m using Zustand mostly for global state, react query for server state. Context rarely.
yes, easier you can use createApi
Best Redux alternative I choose React useContext + useReducer
context kinda sucks
Trust me u would hate it in long run if you understand what impact it is causing once your application becomes complex and large.
it's a pain to implement for us, we used it, and there's just so much to do.
We switched to zustand, and it has never been easier
useContext + useReducer is so complicated. Jotai is SO MUCH easier to implement.
I tried Legend State manager
Is amazing
I wish typescript was t the standard in RUclips tutorials anymore. It's very confusing to see as I'm still trying to understand more complex JavaScript and advanced React stuff. So to through in typescript is a little bit much for me, personally. I feel like it's only really used in very public facing production environments too.
The big channels like Net Ninja, Web Dev Simplified and Academind use JavaScript instead of TypeScript
You will get used to it, not easy at the start but you should learn it.
@@lardosian I feel that lol
I'm no TS expert (still learning phase). But once I touched TS, I don't feel like going back to just JavaScript, it's just that good.
Typescript is really the only tool we have right now to deal with that abomination of a language.
I think best alternative is easy-peasy.
agreed!!
Zustand >
Have u tried Easy peasy ?
i checked, and i think zustand and easy peasy has similar implementation, for *creating a store* that is,
except that with zustand there is no Provider
You forgot mobx
I think you mean "opinionated", not "optionated".
Jotai
easy peasy redux.. 😅😅😅
Valtio is the BEST
coming soon... use-state-global-redux, redux easy =)