Check out more articles:   Building a Scalable Notification System with gRPC and Microservices Adding... Tagged with react, javascript, beginners, testing.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

This post discusses the I/O and CPU performance challenges in React applications and provides solutions to improve performance.

React is Slow, What to do now?

I want to address this point from the article:
<blockquote>
Initiated when a component updates, triggered by changes in props or hooks.
</blockquote>
All component re-renders have the same nature - state change. A component is essentially a function, and when some state changes, React calls that function. The component returns an element, and a Fiber Tree is built from these elements. During the reconciliation phrase, React will compare elements using <code>Object.is</code>. If the result of the comparison is <code>false</code>, then something has changed. React will then check the <code>type</code> of the elements - if the type hasn’t changed, re-render will happen; otherwise, React will unmount the “old” component and “mount” the new one.
Changes in props only matter if the component is wrapped in <code>React.memo</code>; hooks can cause re-rendering if they abstract some state