There's been a lot of confusion and misinformation about Redux going around lately. I just posted "Redux - Not Dead Yet!", which tries to clear things up. Redux is NOT being replaced or deprecated - it's here to stay! But, you might not always need it. http://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet/ …
-
Show this thread
-
Replying to @acemarke @sharifsbeat
Good to hear. Do you think there will ever be a rethink on performance? Currently I need to use selectors to ensure shallow equality on arrays/objects/functions and pull connects to the edges of the tree. I've found a some good tooling to do this but it is fragile and weird.
2 replies 0 retweets 0 likes -
Replying to @sebinsua @sharifsbeat
Selectors are definitely a recommended part of Redux architecture, for both perf and encapsulation: http://blog.isquaredsoftware.com/2017/12/idiomatic-redux-using-reselect-selectors/ … It's possible we might be able to automate things a bit more in the future. I've seen 3rd-party libs that use proxies to detect state accesses, etc.
1 reply 0 retweets 0 likes -
What exactly is "fragile" and "weird"?
1 reply 0 retweets 0 likes -
Replying to @acemarke @sharifsbeat
If I write a selector and somebody refactors it to add an extra property that is non-primitive and not memoized then this will unnecessarily fail a shallow equality check and cause a render. And it's very hard to detect this kind of performance regression.
1 reply 0 retweets 0 likes
I know the library you are talking about `memoize-state`. I'm interested in seeing if it makes this easier for more developers, too.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.