I agree

Agreed

Absolutely !

explains every thing in detail, crisp and clear

Absolutely

damn, thanks for saying that! Really means a lot 🤙

I 100% agree with @Jakezaruba, this video explained it perfectly.

Happy to hear! 🤙

makes me happy to hear!

Will do!

glad to hear it!!!

Glad to hear it! 🤙

Thank you for the kind words!

@@cosdensolutions thank you for the many “aha” moments

Much appreciated! ☺️

I didn't know about the memo either ! Thanks very much.

Thank you for the kind words ☺️

glad you liked it!

Nice! Thanks! Will do ☺️

glad to hear it!

yes, but the goal is not to prevent re-renders, but rather to control them. If you add users, then you have to re-calculate everytime it changes. That's ok. However, if you add a new state variable and change that instead, then the useMemo will not run again. That's what we want, control

the `onChange` function, although it's the same function that does the same code (values don't really matter here), it'll be considered different because it'll be a different instance of the function. Different instance means it's just a copy of the function, but it's not the same one in memory. So even though it looks the same and does the same thing, it is a separate entity, thus it will cause the props to evaluate as not equal

Oh absolutely, very soon!

they're the same, but the second way you'll have to pass all of the arguments manually, if you have some. If you pass it like the first way, they'll get automatically passed

nope, only what is created in a component and is used in the body needs to go there. Event objects are not created in any component.Also, even if you wanted to, you couldn't. You don't have access to the event object to put it there :D

@@cosdensolutions thank you

The goal with this is not to prevent a re-render, but control when it happens. I mention it in the video. If user is a dependency, there's no way around it. The goal is to not have anything else cause a re-render through useCallback, which we did!

@@cosdensolutions Understand, But I really like your video, one of the best tutorials I have ever seen...

This is an excellent point, I am also interested in finding a solution that solves this problem.

Oops.... sorry asked too soon, you explain the problem at 5:00 min when discussing functions in react 🙂

@@unhandledexception1948 Thanks for the question. I've never seen "memo" on a component before now so wasn't sure why, as I too thought react didn't re-render... So my followup question to be sure... should I only use memo on components as in the memo(Search) when I pass functions to the component ? Would passing in a state "setVariable(newval)" function count like the "onHandleX" functions. I've just created a Dummy component with a text property and passed hardcoded text to it then in the component console logged out "rendered". NOT used memo(dummy) -- Even through the property hasn't changed the component renders everytime the page renders. So I don't think react checks for none changing properties. So my next question even for a simple component should we use memo(Dummy) all the time to stop it from rerendering things like titles etc.

Yes it does, but that is what you want. You don't want to prevent a render, you just want to control when it happens. So if there was another piece of state that would change, then it wouldn't re-render. You only want to re-render when what it depends on changes, and nothing else!

@@cosdensolutions cheers. great video as always btw.

only wrap when it's an expensive computation. Otherwise it's not needed!