Timecodes 0:00 - Introduction 00:43 - What is Memoization in React? 07:02 - How to use React.memo in React? 11:51 - When not to use React.memo? 13:02 - Wrapping up & What's Next?
great video but what i found is when we don't use memo in child component and without passing props to child component it also re-renders just directly imported child component . so definition of react memo is not appropriate i.e Using memo will cause React to skip rendering a component if its props have not changed. could you please clarify here? Thanks
Hello Tapas, your viedos are really amazing. crisp explanations, anybody can understand.. i have a question.. What's real use case to use React.memo? have you ever used in your projects? if so, please comment back the use case. For me expensive computation are db calls, but we can't use because url remains same but data keep changing. other than that math operations? it shouldn't be an expensive operations.
Thank you! You have asked a great question. Here is my response: the useMemo hook returns a memorized value. It means it will not resompute the values for the successive occasions. That saves your computation time and make the app faster. Think about operations like search, filter, sort happening on the larger set of data that is already available on the client side. Or you are applying an ML model on a data set available locally on the browser. You may not want to compute it everytime is the same output is expected for the same input. That will be a use case where you want to use this hook. I hope it clarifies!
Timecodes
0:00 - Introduction
00:43 - What is Memoization in React?
07:02 - How to use React.memo in React?
11:51 - When not to use React.memo?
13:02 - Wrapping up & What's Next?
Good explanation of how 'memo' works. Impatient to see the next videos.
🙏
Great video as expected. Tapas makes difficult concepts easy to understand
Thanks a lot, Vishal
Most wanted topic 😊
Thanks! Hope it was clear 👍
great explanation for the infinite times sir @tapas. Thank you.
Thank you very much 💛
❤❤
❤️❤️
great video but what i found is when we don't use memo in child component and without passing props to child component it also re-renders just directly imported child component . so definition of react memo is not appropriate i.e Using memo will cause React to skip rendering a component if its props have not changed. could you please clarify here? Thanks
Hello Tapas, your viedos are really amazing. crisp explanations, anybody can understand.. i have a question.. What's real use case to use React.memo? have you ever used in your projects? if so, please comment back the use case. For me expensive computation are db calls, but we can't use because url remains same but data keep changing. other than that math operations? it shouldn't be an expensive operations.
Thank you!
You have asked a great question. Here is my response:
the useMemo hook returns a memorized value. It means it will not resompute the values for the successive occasions. That saves your computation time and make the app faster.
Think about operations like search, filter, sort happening on the larger set of data that is already available on the client side. Or you are applying an ML model on a data set available locally on the browser. You may not want to compute it everytime is the same output is expected for the same input. That will be a use case where you want to use this hook.
I hope it clarifies!
@@tapasadhikary , yeah I see… Thank you so much for your kind reply