Engineering Manager at Coinbase. Former UI engineer and designer, specializing in React and React performance. Previously at Facebook and Storehouse. Winner of the first Node.js Knockout with Swarmation.com.

ICT Group

Tessa van der Heijden

Elixir

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The article explains why using React.memo, useMemo, and useCallback in components is beneficial and how it helps avoid unnecessary rerenders.

Why We Memo All the Things

Why we React.useMemo All the Props & Deps

Will Someone Please Think of the Children?

But there is also memory occupation involved. Even official doc recommend to use it wisely. Don’t use useMemo untill there is complex computation. React.memo will consume memory to store result. For example if we memoize map operation result of map is stored in memory which is extra burden

If Memo for every component were a good idea, React wouldn’t have made it optional.

This is definitely an interesting point of view, but there are some technical details and benchmarks I’m missing from this article, such as how the decision was made (and how they technically proved that this approach would scale) and what current metrics they are using to measure the impact of this approach

Without measurement, there is no optimization.
Can you provide measurement data before and after optimization?

Tell me you are a shitty lead without telling me you are a shitty lead.