React Today and Tomorrow and 90% Cleaner React With Hooks

Channel:React Conf · Length:1:35:29 · Published:2018-10-26 · Views:1166663

Watch on YouTube

Summary

The first three talks from React Conf 2018, by Sophie Alpert, Dan Abramov and Ryan Florence. They introduce React Hooks and explain the problems with classes that hooks solve.

Why HN recommends it

It is the canonical introduction to hooks, given by the people who built them, and HN uses it to answer questions about why hooks exist.

It's absolutely worth the watch, even if you're somewhat familiar with hooks. — HN, 2019

Web development

Subtitles (excerpt)

Good morning, everyone. Woo! Good morning. Welcome to React Conf 2018. Uh My name is Tom Occhino. I'm the engineering director of the React group at Facebook. I'm really excited to be here. I'm actually really excited to talk to people from all over the country and actually all over the world. Uh and I know joining us on the live stream, we have people from all over the place. So, thank you for being here with us. Before we get started, just a couple of quick logistics. If you haven't read the code of conduct yet, please do so. It's posted by registration. It's posted on the website. Follow it. If you have any issues, please reach out to me or anyone on the staff. The staff is all wearing purple shirts. Uh we got a a great lineup of talks. They're going to be in this room today uh and tomorrow. But, if you need anything else, uh if you need to just get away, if you need to make a phone call, we have room set up actually directly behind me. The breakfast room is available. And in the hallway here, we're going to have the Fiber Arts Circle Knitting Track with Jen Luker. So, check that out as well. If you want to get away from the talks. Uh lastly, there's going to be uh more updates throughout the day.

On Hacker News

Have you seen the ReactConf talk on hooks? [1] It's absolutely worth the watch, even if you're somewhat familiar with hooks. They go through the pitfalls of class-based components and how hooks solve them. It more-or-less boils down to: 1. class-based components force your lifecycle logic to live in disparate locations. 2. Class-based hooks are obtuse with hidden gotchas whereas pure functions te… — kybishop, 2019-09
Hooks require less boilerplate to set up and reuse stateful logic across components If you havent watched it yet, the talk that introduced hooks explains much better than I can: [VIDEO] — jfcisco, 2025-04
Just watch the video from ReactConf 2018 where hooks are introduced (by the dude who built them). You can play along at home quite easily by getting started either with "npx create-react-app myApp" or a simple html file with one script tag to download react from a CDN and one script tag for your code. Talk: [VIDEO] By the end of the talk you'll probably be leaning towards "this sounds cool, I'd l… — AndrewOMartin, 2024-01
You aren’t the only person, I’ve certainly heard it before. But I’m yet to hear a convincing rebuttal to Mixins Considered Harmful [1], the hooks talk [2] or the Motivation section [3] on the announcement. The arguments I’ve heard is that it is “cleaner”, “more understandable” or the OO style is preferred. Some developers feel uncomfortable with hook magic because it introduces a more niche progr… — jasongi, 2022-09
While you wouldn't want to leave "console.log" in your code in production, you can use them in function components just like a classes' render methods. A better example (from the video "React Today and Tomorrow and 90% Cleaner React With Hooks" from October[1]) is something along the lines of updating document.title = `${some} Page` or possibly calling an API. [1]: [VIDEO] — azimuth11, 2019-05

Related videos