Unlocking the Mystery of React's Re-Rendering: Ankita Kulkarni

Unlocking the Mystery of React's Re-Rendering
Your users will not care what tech you used but how fast your app loads. Have you used a hot new stack that everyone loves but still don’t know how to make it performant? Well, it’s because we think about performance as a after-thought after it becomes a bottleneck and when our infra gets costly, ouch! But there is a way to solve this, introducing Core React. We won’t be introducing new tools but going back to how we need to tell React what the DOM should look like. In this talk, we will finally understand why useCallback and useMemo are used, why Lighthouse doesn’t represent performance, how we can minimize component re-render, why it re-renders? and lastly how to profile it with React devtools.

About Ankita

[aristosxanthus]

Never thought about the wasted energy rerendering static components like a logo or button.

[RaducuGabriel]

is nobody gonna say anything about the fact that she is using memo and useCallback like it's a free pie?