Hacker News Reader

I hate using componentWillReceiveProps but always end up doing so because it seems to be the easiest with redux. The static function replacement seems very natural.

View on HN

I'm not shilling, but this is something I definitely don't miss using Mobx.

edit: Ooops, I thought the commenter was referring to shouldcomponentupdate. Sorry for the confusion, please downvote this out of the discussion!

What is the alternative? For when you have a stateful component that "reacts" to new parameters.

Mobx uses observables to monitor what properties you read and collections you enumerate during your render method.

It then uses that information to implement shouldComponentUpdate for you. Each render call refreshes the data use by shouldComponentUpdate.

It gives you 100% percise updating of react components based on state, for free.

Were we not talking about componentWillReceiveProps, not shouldComponentUpdate?

Shoot, my bad. Sorry for the confusion. That is a common common complaint with redux, so I read into it.

No worries, I was just confused what you meant. :)

Is it possible to shill for an open source library which, as far as I can tell, has no monetization path?

If you are going to get technical, ask James Newton-King what Json.NET did to his career trajectory.

It definitely has an intangible value.

Reply on news.ycombinator.com