News for hackers. Stuff that matters.
Re:React Router v4 FAQ by timdorr on Friday September 16, 2016 @01:04PM (#12515464)
It's more that you can get the information about the state of the browser or server's URL down deep into the component tree and then more easily act on it (with a few components, rather than a larger case statement).

It's basically idiomatic JS vs idiomatic React/JSX.

Re:React Router v4 FAQ by kfinley on Friday September 16, 2016 @04:28PM (#12517097)
That's a fair point. Kind of like adding a redux @connect in a child component.

Edit: To the idiomatic point. The first thing that struct me when using React, was that instead of having to use a custom Component for a for loop I could just use someArray.map(). I see this as a similar situation.