I feeling I have found a gold mine when I found this channel. It's a fantastic way to learn both typescript and get to know the current state management options in react
Have never heard or seen Jotai. So interesting these different state managers. I still think I'll just stick with Redux or React Query. I'm really loving React Query and trying to use it when I can. Appreciate the content Jack. Much love and respect my friend!
Yeah, I need to do some more stuff on `react-query`. Tanner is doing an awesome job on that. And I'm intrigued about the potential of it getting integrated into Jotai so that any atom can be its own managed query.
Love the channel! Can you help me understand what's going on here? The project builds, but I just get a white, blank page. ./node_modules/framer-motion/dist/es/components/AnimatePresence/index.mjs Can't import the named export 'Children' from non EcmaScript module (only default export is available)
I'm curious, if you had to choose one or the other which would you choose between Jotai and Zustand for a state manager? Let's take managing user auth and say a cart state? I used both to write logic for managing auth state and a color palette state, I found both very good libraries but I wanted others input on if they had one what would they use.
Personally I would choose Jotai because I'm fascinated by atomic state and I have a hunch that it's the future. Professionally I would choose Zustand because it's simple, conventional, and very popular.
@@jherr thanks for the response. I was watching your video on react context as a state provider a bit ago and when you showcased Zustand , I enjoyed how simple it was to implement + it didn't cause any unnecessary re-renders (I'm comparison to say react context patterns I see). My question I guess would be with Jotai would it cause re-renders similar to react context since it needs a provider as a HOC of sorts? Not sure if I make sense or not.
@@quelchx Jotai has the same performance in terms of re-renders as Zustand. That being said, I think there is a lot of unnecessary concern about re-renders. React is VDOM framework that is optimized to handle re-renders very quickly.
Jotai state appears to only be accessible within the jotai atom get/set functions or in the React component context. So I would set an external value in the atom set function and then use that value in Axios. I'm assuming you are storing the JWT in an atom.
@@jherr I guess the main contrast would be with prop drilling and more significantly (IMO), utility components with "onChange" callbacks littered everywhere.
I feeling I have found a gold mine when I found this channel. It's a fantastic way to learn both typescript and get to know the current state management options in react
True, true.
Have never heard or seen Jotai. So interesting these different state managers. I still think I'll just stick with Redux or React Query. I'm really loving React Query and trying to use it when I can. Appreciate the content Jack. Much love and respect my friend!
Yeah, I need to do some more stuff on `react-query`. Tanner is doing an awesome job on that. And I'm intrigued about the potential of it getting integrated into Jotai so that any atom can be its own managed query.
Awesome as always! Thank you, Jack.
awesome work ! Clear and easy example thank you Jack
Thanks for the awesome content, Jack!
Jack has a really nice calm voice!
Hello Jherr - this series is always interesting. Thanks.
Such a good video! Thanks Jack
Love the channel! Can you help me understand what's going on here? The project builds, but I just get a white, blank page.
./node_modules/framer-motion/dist/es/components/AnimatePresence/index.mjs
Can't import the named export 'Children' from non EcmaScript module (only default export is available)
Underrated channel
We need more of jotai vs recoil or in depth on both. Would be amazing.
Thank you, I will get it a try.
Great content 👍🏽
I'm curious, if you had to choose one or the other which would you choose between Jotai and Zustand for a state manager? Let's take managing user auth and say a cart state? I used both to write logic for managing auth state and a color palette state, I found both very good libraries but I wanted others input on if they had one what would they use.
Personally I would choose Jotai because I'm fascinated by atomic state and I have a hunch that it's the future. Professionally I would choose Zustand because it's simple, conventional, and very popular.
@@jherr thanks for the response. I was watching your video on react context as a state provider a bit ago and when you showcased Zustand , I enjoyed how simple it was to implement + it didn't cause any unnecessary re-renders (I'm comparison to say react context patterns I see). My question I guess would be with Jotai would it cause re-renders similar to react context since it needs a provider as a HOC of sorts? Not sure if I make sense or not.
@@quelchx Jotai has the same performance in terms of re-renders as Zustand.
That being said, I think there is a lot of unnecessary concern about re-renders. React is VDOM framework that is optimized to handle re-renders very quickly.
@@jherr appreciate your input and time -- thank you 🙂
5:35 tf todo do todo into the todo got me tripping brah
Can you please make an example where adding and setting a todo use an async atom?
How can access the jotai state in Axios interceptor
Jotai state appears to only be accessible within the jotai atom get/set functions or in the React component context. So I would set an external value in the atom set function and then use that value in Axios. I'm assuming you are storing the JWT in an atom.
Do you have sample that does not use typescript? Every sample I see are using typescript that makes me more confused
React + TS + atomic design (atoms, molecules, organisms, templates, pages etc..) + Jotai = ❤️❤️❤️
I am confusion
There's a simplicity to this that I just love.
What would you say to people who feel it is too similar to global state?
So when you say global state do you mean redux? Because there are a bunch of state managers and the my have different ways to model state.
@@jherr I guess the main contrast would be with prop drilling and more significantly (IMO), utility components with "onChange" callbacks littered everywhere.