Member-only story

React: React 15 vs React 16

Eishta Mittal
2 min readMar 11, 2024

--

My career started with the release of React 16 in 2017 and since then it has been with me. I think I can consider as my better half now.

So, lets see what React 16 offered me that I couldn’t say NO to it.

React 15 vs React 16 :-

1. Fiber Reconciliation Algorithm:

  • React 15: Used the stack-based reconciliation algorithm.
  • React 16: Introduced the Fiber architecture, a complete rewrite of the reconciliation algorithm, enabling better performance and asynchronous rendering.

2. Error Handling:

  • React 15: Lacked comprehensive error boundaries, leading to full application crashes on JavaScript errors.
  • React 16: Introduced Error Boundaries, allowing components to catch and handle errors within their subtree, preventing crashes and providing fallback UIs.

3. Rendering Improvements:

  • React 15: Rendered components synchronously, leading to potential performance bottlenecks.
  • React 16: Implemented asynchronous rendering with Fiber, enabling more efficient scheduling and prioritization of updates, resulting in smoother user experiences.

4. Return Values:

  • React 15: Required a single root element in the return value of a component’s render method.
  • React 16: Allowed returning

--

--

Eishta Mittal
Eishta Mittal

Written by Eishta Mittal

Software Engineer passionate about Frontend Engineering

No responses yet