This is what I was trying to say in my last comment and convey in the article but I did a shitty job. I meant to say that by not connecting redux state to the component, the component won’t re-render on state changes. Clearly mapDispatchToProps won’t affect that as it’s not changing, but you’re right, what I said in the article implies the opposite.

I should also add the disclaimer that if the state updated here is included in mapStateToProps in another component, that component will be subjected to hella re-renders as well, so care must be taken.

Super good point regarding passing the action creator directly to connect though. I’ll update the article to reflect that and also be clear on what exactly triggers the re-render. Thank you!

As you mentioned at the end, importing the store to listen to changes was still necessary for tracking state for things like tweens and rapidly changing values.