Видео

This was just amazing! subscribed.

How should I decide when to use this approach or react memo? I love your videos btw

Golden 🙏

Thanks so much for creating this type of content, it's so engaging and interesting to watch. After watching this I became curious about the virtual dom, is there any way to see what it actually looks like in a real React app?

❤❤❤❤

So??????? Where is the next episode? My baby is crying for it... <3

I genuinely admire your work.. it’s simply outstanding.

Thank you, really good video

Fantastic Explanation Love from India

How can I check the time?

have you thought of releasing a react 19 course so you can take my money?

Thanks for Great explanation , but want ask about create component inside another we can use useCallback to create component it works fun ?!! ex const CustomInput = useCallback(() => { console.log("rendering custom input"); return <input placeholder="test custom input" />; }, []);

I honestly wished i could like this video twice!

You are truly an expert if your craft. I’ve watched other 1hr videos explain the solution to re-renders and still don’t get it. Ty so much! I’m buying your book.

THis is definitely the clearest explanation on uselayoutEffect. Everyone else is just mentioning the "it does things synchronously" and thats it.

Really valuable, thanks!

Really good!!

Please , dont stooppppp !!! You're f*cking amazing !!!

One clarification, for the last scenario still we can send the SlowComponents as children to the Layout component like <Layout>{[<SlowComponent key={1}/> <BunchOfSlowComp key={2} />]}</Layout>.

Hi, really nice videos, what theme do you use for the code, it looks very nice?

Hi great videos thanks! How did you make your code animate from one to another?

This is simply the best explanation

Best explanation of react design patterns i've ever seen

It's wrong pattern. You should never use it. Read react docs, "If you’re not trying to synchronize with some external system, you probably don’t need an Effect."

Just thinking crazy (to check if I understood OK). Could you also avoid re rendering you mention if you code the example like this?: Instead of passing a prop with "content", create a Content component and export it, then import that Content in ScrollableWithMovingBlock AND assign it to a ref like: cont myContent = usRef(Content), and finally rendering it like: {myContent.current}

Like how????? How much efforts you have taken so far! You are gem !!!

FYI, I think there's an error on this page: ruclips.net/video/pNaW0Md2o0g/видео.html I think the closing tag should be: </ScrollDetector>

really interesting unique video series .thanks

Found this after my interviews 🥲. Definitely need a complete video series on advanced concepts.

thanks.. very informative

Thank you for explaining the myth about props changes not triggering re-render. I've been confused about this for a long time and finally many things become clearer.

When state is true the create element is call for Input and when state change to false , we have another createElement , why Input's have same reference?

Great series, I keep coming back to it time and time again. At 9:12 you mention if a component is wrapped in React.memo and it's re-render is triggered by the parent and "only" by the parent, then React won't re-render the memoized component. I may be misunderstanding, but is that to suggest that if state changes higher up in the element tree where 'Parent' is used, that the memoized component (MemoChild) will always re-render?

Excellent ! Brilliant explanation.

quick question: where have you been these past 2 years when I was starting to learn react?

Am I wrong in thinking that we could achieve the same result using the useRef hook to hold the scroll position, given that useRef does not trigger re-renders and is powerful for direct DOM manipulations

hey i really loved your contents but gonna see your blog if you had added react 19 into content.

Amazing video 🎉

didn't get reset part going to watch again.

i don't quite get what you mean by last sentence........

when video started i feel this is not way nadia teaches she doesn't explain why remove it.

love from manish gupta, i start loving you after watching your content. :)

when i stuck on how to improve my react code i come across your video, after watching that video i started seeing from your first one. going to see all and implement in my code and after reading comment i found out you have a blog also going to watch that. i will appreciate you content more often.

This was such a quick, simple and clear explanation! Really appreciate the effort and time it took to do such wonderful work, thank you a lot!

it's just the first episode, but i'm already solved a lot of re-rendering issues. Thank you

Thank you

Very good content!

fantastic video !!! but i have one doubt i hope you would explain me this better so my doubt is in this video code example you are using HeavyComponent and everytime the parent component will re render the HeavyComponent will also re render but in react they say that in component only that part will be re render that is got changed and other element will not re render so here why heavyComponent will re render again even it will be same for all re renders of parent component.

amazing explanation