React- useCallback Invalidates Too Often in Practice

What is issue #14099 in React’s repo and how it affects you?

Vitali Zaidman
May 25 · 3 min read
Image for post
Image for post

Why do we need useCallback in the first place?

A naive code where a pure heavy component is re-rendered on every re-render of its parent.

This is where our useCallback comes into play

Here the pure heavy component is not re-rendered on any render of its parent after the first one.

The Issue With useCallback

Workarounds

Class Component

Using class components

useEventCallback

A Possible Future Bug Fix

Summary

Related articles you might find useful:

Welldone Software

The leading full-stack consultancy.

Vitali Zaidman

Written by

https://twitter.com/vzaidman ⎝(•ω•)⎠ https://vzaidman.com

Welldone Software

The leading full-stack consultancy. Creating amazing frontends and rock-solid backends using top notch technologies and practices. Visit us at https://welldone.software.

Vitali Zaidman

Written by

https://twitter.com/vzaidman ⎝(•ω•)⎠ https://vzaidman.com

Welldone Software

The leading full-stack consultancy. Creating amazing frontends and rock-solid backends using top notch technologies and practices. Visit us at https://welldone.software.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store