React Performance Debate

Discussions debate React's performance overhead from virtual DOM diffing and re-rendering, questioning its efficiency benefits versus alternatives like avoiding React altogether.

📉 Falling 0.4x Web Development
4,458
Comments
18
Years Active
5
Top Authors
#9148
Topic ID

Activity Over Time

2007
1
2010
1
2011
2
2012
17
2013
31
2014
191
2015
384
2016
311
2017
371
2018
304
2019
397
2020
346
2021
364
2022
502
2023
482
2024
352
2025
375
2026
27

Keywords

formik.org JS FPS Children.only PR UI MVC ReactTraining React.memo PureRenderMixin react dom component render rendering async virtual performant rendered js

Sample Comments

sarchertech • Sep 16, 2025 • View on HN

If react adds extra render time and extra dev time, what is it saving?

jonahx • Nov 1, 2014 • View on HN

Doesn't React already do efficient DOM updates for you with their virtual DOM and it's diffing mechanism? Or are you referring to something else?

ibash • Aug 17, 2024 • View on HN

People forget what problem the virtual dom and react is supposed to solve.No better article than this: https://blog.vjeux.com/2013/javascript/react-performance.htm...

programminggeek • Feb 29, 2016 • View on HN

Perhaps the answer is to not use React.

arthurcolle • Aug 10, 2021 • View on HN

still more performant than modern React based systems

pkstn • Dec 31, 2019 • View on HN

I have easy solution: don't use React!

driverdan • Jan 1, 2014 • View on HN

It sounds like you've never tried using React. It has built in solutions for the issues you mentioned.

nikivi • May 14, 2020 • View on HN

Perhaps it's due to React's architecture of one way data flow?

foota • Nov 3, 2015 • View on HN

Isn't this supposed to be a non issue because react can intelligently compare the higher level components of your application and decide whether they need to be re-rendered?

linkmotif • Dec 29, 2017 • View on HN

Who complains about React being slow?