Viewing profile — dounan

You're right. I misinterpreted your first comment to refer be referring to React elements, which is quite different from DOM elements https://facebook.github.io/react/blog/2015/12/…

> Correct me if I'm missing anything! You're not missing anything :) That approach also works. The important point is that you have to pass the extra index prop down to the child t…

That's a great point, and being aware of the dangers of shouldComponentUpdate is what this post is all about. There are a lot of gotchas when using PureComponents, and can lead to …

I've updated the post to say 'in the right places' instead of 'everywhere' until we get some profiling data.

In our experience, React is not necessarily 'slow' by default. Re-constructing parts of the element tree each time can be a bit wasteful, but it is only as slow as your render() me…

First off, thanks for your work on React! Makes all of our lives easier as developers :) As dmnd pointed out, I'm not entirely convinced that dropping PureComponent everywhere is n…

For this specific example you don't have access to the list index in the constructor. In general binding like that in the constructor works only if you depend on props, but at that…

Atom editor with the 'One Dark' theme

nit: new component instance (not element)

> I guess they just call that function from within the Data component with the correct parameter. Yep > Is there a better way? We're experimenting with some other options internall…

The reason arrow functions and bind don't play well with PureComponents is that they return a new function instance each time. This means that the Data pure component will wasteful…

Haven't tried this myself, but this might be what you're looking for: https://github.com/facebook/react-native/issues/9146#issueco...

Even though you picked the final designer as the winner, how did he know you were actually going to pay him?