Hacker News Reader

Not sure if sarcastic comment, but this would entirely break how redux works.

Redux is designed to be used with this kind of pattern. Immutable.js, which is often paired with it, mostly solves this particular type of performance problem. You'll still have a performance ceiling when you use Redux, but it's very unlikely that you'll hit it.

Edit: I was using Immutable.js as a stand-in for immutable data structures in general; apparently there are other JS libraries you can use

Hi, I'm a Redux maintainer. I personally would recommend _against_ using Immutable.js, for a number of reasons [0].

Instead, I highly recommend the Immer library [1], which lets you do immutable updates with "mutating" logic in callbacks.

Even better, try out our new Redux Starter Kit package. It uses Immer internally to let you simplify immutable updates in your reducers [2].

[0] https://www.reddit.com/r/javascript/comments/4rcqpx/dan_abra...

[1] https://github.com/immerjs/immer

[2] https://redux-starter-kit.js.org/

Yikes, please no. Mutating your state will put you in a world of hurt.

I probably wouldn't worry about it unless you have really large arrays. It's still probably pretty insignificant compared to the time spent updating the DOM.