Oh dear. Yeah, per that FAQ, the earliest advice from Dan was to just connect once or twice at the top of your app, but that early advice has been totally supe

Oh dear. Yeah, per that FAQ, the earliest advice from Dan was to just connect once or twice at the top of your app, but that early advice has been totally superseded by now. You should _absolutely_ go ahead and connect _any_ component where you feel that doing so helps simplify things, especially in terms of props passing. I discussed some of the major aspects of Redux-related performance in my blog post "Practical Redux, Part 6: Connected Lists, Forms, and Performance" [0]. That includes info on why more connected components is generally better for perf, as well as usually making it easier to understand a given component's data needs. You may also want to read through some of the articles in the "Redux Architecture" [1] and "React/Redux Performance" [2] sections of my list, particularly the post "High Performance Redux" [3]. Hopefully that info helps. Please let me know if you've got any further questions or concerns I can help with! [0] http://blog.isquaredsoftware.com/2017/01/practical-redux-part-6-connected-lists-forms-and-performance/ http://blog.isquaredsoftware.com/2017/01/practical-redux-par... [1] https://github.com/markerikson/react-redux-links/blob/master/redux-architecture.md https://github.com/markerikson/react-redux-links/blob/master... [2] https://github.com/markerikson/react-redux-links/blob/master/react-performance.md https://github.com/markerikson/react-redux-links/blob/master... [3] http://somebody32.github.io/high-performance-redux/ http://somebody32.github.io/high-performance-redux/