React Today and Tomorrow and 90% Cleaner React With Hooks

The first three talks from React Conf 2018 by Sophie Alpert, Dan Abramov, and Ryan Florence.

[tom]

love watching dan speak, he clearly loves talking about react and he can explain new features so succinctly. the master.

[rayt]

44:17 “with hooks we separate code not based on the lifecycle method name but based on what the code is doing” - game changer, Thanks Dan!

[motozirillo]

Its not often that you get to experience the same library for the first time twice. Hats off to the React team for their great work

[jamiekyle]

The React team are killing it with Sophie managing. The last year has been incredible for React and it just keeps getting better and better

[Pol-jjmy]

I have the same feeling of excitement watching this than the one I had watching Apple keynotes back in late 00's!

[frewinchristopher]

You can tell by all the people laughing whenever Dan mentions binding functions (and that fact that even he forgets to bind a function) that it has always been a pain point... but hooks will totally remove that boilerplate!!

[SolidSnakeBA]

But does it have a battle royal mode ?

[mrmupfukudzwa]

The React team is the only team in this world that i look at and say...'Damn, i wish i was a part of it'. React really rocks, and its always exciting to see what they are coming up with.

[naythaniel]

This API is beautiful. I really don't know how else to describe it. It's just a gorgeous API.

[andriirubtsov]

Ryan Florence is a fantastic presenter

[emmanueldalougou]

Abramov is a genius a master of React. i thnk that he breathe react

[wnyao]

Great efforts from the react team and react community. Inspiring. 💙👍🏻

[ln]

From a functional point of view, I would argue that the 'withState' function from 'recompose' is a better choice than the 'useState' hook, because useState makes the functional component not pure, it takes input from the caller (props) as well as the useState function, whereas withState will merge the state (name, setName) into the props, so the functional component only takes props as input. Also you have to use useState as a statement, so there is no way to write the functional component without a function block (the curly braces).

[dulanjala]

nice work... they have been working hard on it...! and they do feel like they are too developers like us not magicians... one of the Greatest Conf I have watch.... Perfect....!!!

[dulanjala]

how little things can make us So Happy...!!!

Bye `class`, might the force be with you

[ombieautopilot]

Wow it gets a lot loader at around 27 minutes

[Anonymous-gwn]

Awesome work, but I wonder why not let the the sideEffect function to accept parameters what can be parameters of useEffect so the engine don't need to declare a new anonymous arrow function every render. I know it's not a big problem but it has no harm to current pattern and might have a performance improve about maybe less then 0.1%.
Since react is favor of explicitation, then should it be better to explicitly declare what parameters the sideEffect will use instead of reading it from the execution context?

[lednhatkhanh]

So excited, can't wait to use hooks in react 16.7

[Pop-zbwr]

Great talk, I will start using hooks. One point though, electrons don't orbit :)