ImmutableJS: worth the price?
Alex Faunt

While I relate to some of the irritations described here, it’s my understanding that the chief value of Immutable.js is being able to do shallow comparison inside shouldComponentUpdate in order to short circuit unnecessary render cycles. In an app with a lot of data and logic to render, say, visualizations, that’s crucial because virtual DOM and reconciliation still cost something even if not as much as rendering actual DOM. If there’s an answer to this I don’t know about, I would love to hear it, as I am in a greenfield stage and would love not to use Immutable if I don’t have to.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.