Andrew Clark - Recomposing your React application at react-europe 2016

[@lordcdubs]

Fantastic talk, think you've hit the nail on the head as to why you would want to decouple pieces of a react component and how to reasonably compose them together! (and in a functional manner no less!)

[@evolutionxbox]

I'd love to see an updated talk using React hooks.

[@JacobRuizDesign]

Really enjoyed this talk. Thank you!

[@LunfardoAR]

I'm kinda new to redux and got little confused at 5:08 where he calls fetch inside componentDidMount(). Shouldnt async functions go in thunk-middleware and calling actions in the process?

[@meida_fpv]

Ignacio Torres that's the common "best practice" when using redux, but I think in this case he was simply trying to keep his example as simple as possible.

[@frantzdae]

You won't necessarily use React together with redux. In that case data fetching could work inside a lifecycle event. Of course your code gets pretty messed when you have a complex UI. That's why redux (and friends) are a good abstraction strategies.

[@anonymousBl1]

Great talk! I didn't understand though how he "squashes" components (kzbin.info/www/bejne/sHXCm6iaepKVjs0m22s - 22: 22) ? when i'm using recompose i still get a lot of components. any ideas ? thanks

[@adamzaczek6342]

And that's how hooks came to life

[@catwhisperer911]

The render method of the container class returned by fetchResource is wrong. It should return , not . Otherwise very nice presentation and thanks for sharing.

[@preechasattabut9850]

Me too ...

[@miketembo5481]

great just at the right time

[@vyorkin]

great talk (ohuenno)

[@user-ug8qc6tr6b]

Ohuenno Indeed

[@PierreEricMarchandet]

Thanks for sharing. Really inspiring.

[@oliveirasantos6174]

Pena q não entendo o inglês 😢

[@luknei]

Awesome, thanks!

[@janakathilakarathna1639]

Awesome ^_^

[@harshitpant3067]

Rip recompose