React, Inline Functions, and Performance
Overall, I think the post is a little too dismissive about the performance implications of bind, and says a new function trigger rerenders.<p>In IE 11 and Safari for example with Babel transpilation, arrow functions are going to eat your frame rate alive, especially if you have a text input handler with some sort of validation around it. Even in latest Chrome and Firefox, you end up with inputs that feel slow.<p>I agree PureComponent and object equality cancel the benefits of each other out a good deal of the time.<p>The pure without handelers approach has the notable exception of a sortable table with inline editing, or even checkboxes, where row index of the handler matters.<p>Ultimately, it is better to make new devs to react aware of avoiding bind in render, than it is to retroactively add constructor placed binds in the app when frame rates are below 25-30 by default. Something I’ve seen quite a bit in redux apps.