React Today and Tomorrow and 90% Cleaner React With Hooks
React Conf4 HN recommenders · recommended in 4 months, 2019-2025
1.2M views · 8 years ago · talk · dated
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.
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.
27:45React.js Conf 2016 - Ben Alpert - What Lies Ahead
Meta Developers
50K views • 10 years ago
25:47React.js Conf 2015 - The complementarity of React and Web Components
Meta Developers
22K views • 11 years ago
31:17React.js Conf 2015 - Hype!
Meta Developers
108K views • 11 years ago
31:11React.js Conf 2015 - Immutable Data and React
Meta Developers
159K views • 11 years ago
35:32Cheng Lou - On the Spectrum of Abstraction at react-europe 2016
ReactEurope
63K views • 10 years ago
29:32Pete Hunt: React: Rethinking best practices -- JSConf EU
JSConf
548K views • 13 years ago
40:58Pete Hunt: React - Rethinking Best Practices (updated) - JSConf.Asia 2013
JSConf
58K views • 12 years ago
4:40React.js Conf 2016 - Lightning Talks - Elie Rotenberg
Meta Developers
4K views • 10 years ago
44:36Hacker Way: Rethinking Web App Development at Facebook
Meta Developers
900K views • 12 years ago
36:45Jordan Walke - React to the Future
ReasonConf
48K views • 6 years ago
18:55[JSConfUS 2013] Tom Occhino and Jordan Walke: JS Apps at Facebook
JSConf
45K views • 13 years ago
31:48Lin Clark - A Cartoon Intro to Fiber - React Conf 2017
Meta Developers
216K views • 9 years ago
36:45Rich Harris - Rethinking reactivity
You Gotta Love Frontend
334K views • 7 years ago
12:01React without memo
React Conf
150K views • 4 years ago
24:28Sebastian Markbage: Minimal API Surface Area | JSConf EU 2014
JSConf
71K views • 12 years ago
35:25Pete Hunt - The Secrets of React's Virtual DOM (FutureJS 2014)
Codegram
75K views • 12 years ago
33:25Dan Abramov: Beyond React 16 | JSConf Iceland
JSConf
139K views • 8 years ago
25:55React.js Conf 2015 - Beyond the DOM: How Netflix plans to enhance your television experience
Meta Developers
26K views • 11 years ago
30:41Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015
ReactEurope
472K views • 11 years ago
1:03:48JavaScript: The Good Parts
Google TechTalks
589K views • 17 years ago
5 comments from Hacker News
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: ▶ this video
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: ▶ this video By the end of the talk you'll probably be leaning towards "this sounds cool, I'd like to play around with it" or "that sounds like cursed incantations for the damned".
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 programming concept than OO (e.g stateful functions). I don’t find these arguments compelling. What the React team managed to do was reproduce the same functionality as class components while decreasing the footguns associated with them. 1. link 2. ▶ this video 3. link
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 tell you exactly what they're doing. 3. A whole class of unergenomic solutions disappears when you use hooks. [1] ▶ this video
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]: ▶ this video