Stop worrying about React Re-renders so much (an overview of the react profiler with refactoring) 

Developers will usually have faster machines than users. And users will do more than just use your one app. Not worrying about performance and resource usage is how we get terrible apps like MS Teams

The human eye only being able to recognise 30 fps is a myth. We're able to notice far more than that. It's said that 24 fps is required for us to interpret video as motion. I don't know how precise that number is however. I can see a clear difference between frame rates even upwards of 100 fps, after that the updates are too frequent for me to notice a difference. However, some people can notice even more frequent changes. We might not necessarily be able to react to all changes however. Our eyes don't use a concept such as frames to begin with, we continually interpret changes, and how well we process the information depends on ability, and that can be improved through training. However, being bothered by a change that takes far less than 1/30 of a second is pointless as you said. I'd say about 50ms is within an acceptable range when it comes to responsiveness.

In my experience, you as a developer can simply never see any slowdowns while some of your users are getting a terrible experience. In my specific case problem is the AMD CPUs especially on Firefox.

Great video! I've been exploring various blogs and videos to gain insights into React re-rendering. Your video provides an excellent real-world perspective on the topic.

Thank you for your video it was very clear. Can you please do a video when you explain in details the useMemo and useCallback and when to use them. I would appreciate it.

Great video but not for everyone. I develop web apps using react three fiber (a react based wrapper around threejs) for building 3d experiences. Where your application needs to run at 60-90 fps, and even the smallest things can cause a frame rate drop, avoiding react to re-render lots of times becomes a very important thing

I always say that computation isn't the biggest issue anymore. But rather network calls are. However, I still find myself trying to optimize rendering prematurely..

3:13 as a gamer, this statement is complete pain. Nice vid tho.

The only thing this video does is explain why you SHOULD be concerned about re-renders

awesome video! thank you so much!

Good job babe!!!

Great video, but what you said about 30fps is a myth. Apologies if the joke flew over my head.

Great video, keep it up!

Great video, thx!

How to decide when to use memo vs just pulling the component to a higher state?

When do u recommend shifting to state sharing tools like Redux Toolkit over React context?

i'm not a react dev, right now, the big problem react has for me is not re-render, it's all those crazy hooks they have.

It's not a shadow DOM It's a virtual DOM. Two completely different things.

"A human cannot detect higher than 30FPS". All future opinions stated, discarded

@1:25, shouldn't you have said "... what the VIRTUAL DOM looks like..." instead of SHADOW DOM?

So re rendering here only means re rendering the vdom right?

3:15 The human eye can see way above 30fps