React is a popular JavaScript library for building user interfaces. One of the key features of React is its reconciliation mechanism, which is the process by which React updates the user interface…

Medium_JS is a curated collection of insights and tutorials on JavaScript development, designed to help developers stay informed and inspired in the ever-evolving world of web development. By featuring a selection of high-quality articles, tutorials, and expert opinions from the JavaScript community, Medium_JS offers  guidance on mastering JavaScript language features, exploring modern frameworks and libraries, and solving common development challenges. Whether you're a frontend developer, a full-stack engineer, or an aspiring JavaScript enthusiast, Medium_JS provides a  knowledge and resources to fuel your JavaScript journey.

Medium

Reconciliation is the process by which React updates the UI in response to changes in data. It is a key feature of React that enables developers to build applications that are fast, responsive, and maintainable. By understanding and optimizing the reconciliation process, developers can build efficient and performant applications with React.

Optimizing React Components with the Reconciliation Mechanism: Tips and Best Practices

How to optimize the reconciliation process in React

<a href="https://app.daily.dev/philongn" data-mention-id="VMWITFfzVtUrSJ7P8v5pD" data-mention-username="philongn">@philongn</a> You are correct that React.memo will still rerender a component when its state or context changes, even if the component does not use props. In the case of the example “MyComponent,” wrapping it in React.memo would not provide any additional optimization since the component’s local state is the only thing that changes.
However, I did not intend to demonstrate the use of React.memo in that example, but rather to show how a change in local state affects the reconciliation process.
At this point in the article, I have not yet discussed React.memo.
I hope this provides clarification.

Such a bad article 🫣 read React docs once again, please

Great guide, I’ve seen plenty of performance issues as a result of missing useMemos.

This is not legit info. In short, we use memo to memoize props coming to components. From parent -&gt; children. That’s it. We also have inside memo function a second parameter, which allows us to check in deep comparison, rather then check by shallow comparison