Introducing Jotai || React State Manager Tutorial

Let's try out the new Jotai state manager.

Hope you folks enjoy this!
👉 If you enjoy this video, please like it and share it.

💢 Watch our other videos:

Thank you for watching this video, click the "SUBSCRIBE" button for stay connected with this channel.

#javascript #reactjs #jotai

[ljuglampa]

Yeah Jotai is really clever and also performant. Ever since I discovered react-query I noticed 90% of my global app state was actually cached server state so it makes sense to let a good caching solution like react-query take care of that. After that Redux was really overkill. I really like this new wave of hook based state management libs. Kind of feels like a new (improved) React era!
Thank you Jack for your constant small walkthroughs of new tech. Perfect format! :) Could you do a Q&A video maybe? I'd like to know more about you, your development history, family situation, all that :) Take care!

[realyozza]

Audio quality makes me watch more of your work! Thank you :)

[eugenethered]

Wow... super elegant, thanks Jack for the superb explaination!

[CodingAfterThirty]

Haven’t heard of this yet, but am excited to try this out in my next project. Great video.

[danielgabriele]

Thanks for your work. Much appreciated. So many options out there.

[matej-world]

On a first look looks cleaner than zustand :)

[TheNerdyDev]

That looks interesting. Need to check, Jotai ! At first I thought it is a new Pokemon 😂

[eleah]

And easier to pronounce than Zustand! Thanks. This is really interesting.

[seanknowles]

Would be great to get a more indpeth look at DX regarding atom/service composition with async crud operatoins in an app. Would love to see how to combine utility async or service code with atoms and how to structure them in a large application, seperation of files and also maybe using hooks... Either recoil or jotai would be great!

[lukerocco]

Great content as always. I don't agree 100% about the Provider wrapping App. Jotai works in provider-less mode. Using Provider does have it's use cases, but most of the time, provider-less is the way to go (as recommended in the official course). Without a provider, an atom's value is the same through out the entire app. You can use Provider to isolate state and use the same atoms in different places (i.e. children of different Providers), without affecting each other.

[danielalonge]

This is quite interesting
I hope you would explore best use cases, merits and demerits of this state management package

[delcambrem]

What about using Jotai across different components? I'm trying to set up a simple two-component project just to test Jotai, but I can't get it to work

[creative-commons-videos]

I am not sure what is the benefit of using this over recoil ? which is maintain by Facebook ????

[WikiPeoples]

I've never seen a fucking framework need so many additional libraries to solve something as basic as state. Jotai, Recoil, Redux, Mobx, Hooks, Class Components, the list goes on and on and on... This all points to a serious design flaw in the underlying REACT technology. Do you know how many state management libraries you need when writing native iOS or Android apps? None. Because this problem of managing state, avoiding re-render cycles, etc... ISN'T a problem. Imperative code just works without "gotchas" that require weird frameworks that "solve" the never ending state problem.

[jogre]

awesome but i dont get it the suspense error while removing the fetch. any please?

[wonka]

Can you use jotai in class components? I can't find information. My current project at work we use almost all class components.

[louispetrik]

So, If I want to use the atom state in multiple components, that each have a single file, should I create one file for the state, that holds the atom, and then import it in every component file? I tried to figure it out, and this seems to be the only working way - inside each component file, I can use useAtom, and pass the imported atom into it.

[alexalannunes]

amazing video.. but how I handling api errors or any error

[mrkhoros]

This is useless because the tutorial does not use the provider properly and all the code is written in one page. This makes no sense since you must use useState for such examples as nothing is going down any level and once a const is defined the whole page has access to it. thumbs down.