These are chat archives for jdubray/sam
it allows you control whether a re-render occurs.
Use shouldComponentUpdate() to let React know if a component's output is not affected by the current change in state or props. The default behavior is to re-render on every state change, and in the vast majority of cases you should rely on the default behavior.
that's a horrific coupling a component should not know anything about that. It has to be orchestrated from below.
The default behavior is to re-render on every state change
yes, that's my problem with React
that's a horrific coupling a component should not know anything about that
the component doesn't have to know about it, just like when we use
ReactRedux.connect() we're binding information from the state to the view.
there’s a shift in Redux community from Immutable.js to Ramda or lodash/fp
I am so surprised! :-P
then there is this comment:
Actually, how Google Engineers think web development should be is Polymer — not Angular. At Google’s I/0 17 there was maybe 2 Angular talks and about 10+ Polymer talks.
I am not too surprised, Angular does look like it's dying a bit, but at the same time, I feel for a big IT shop building standard IT stuff, that's a stable, robust choice.