-
-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are we supposed to use memo wrapping while using jotai ..? #324
Comments
There's nothing bad about re-rendering. It will be bad if it decreases performance. You can use the memo there, and maybe there are other approaches instead of the memo. I recommend you this. But I'd love to see where's the problem in jotai and your performance so that we can help you more. |
@sahilrajput03 |
Gonna read this article and get back to you..., thanks for replying ..:) #but some people do say that you must use react.memo as comparing dom nodes while checking if dom needs updation is more intensive than comparing props(react.memo) in any app. I do understands that profiling is the best way if something needs render minimazation though..i am little confused.., will read the article by dan abramov and will get back here..!. |
I just came to know about jotai from reading kent'c article about statemanagement.., but i am using this for my curren projects.., i am tired of making all contexts and their providers using usecontext.. 🤣 Thanks a lot for making jotai this good..! |
Check my latest todos example, using memo. |
I saved that codesandbox in my folder in codesandbox account, and will analy it sooner. |
since if we don't wrap components around React.memo, react re-renders all child components by default, is there some recommendations for using react.memo around each component for using jotai effectively.?
Jotai is great work, but i also made a similar thing some time ago when i din't know about it then.. https://www.npmjs.com/package/usewhat , but its far different thing from jotai, thanks!!
Loving uisng jotai!!
The text was updated successfully, but these errors were encountered: