Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    React without memo

    React Conf

    1 HN recommender · recommended in 3 months, 2022–2023

    YouTube

    12:01 · 150K views · Dec 9, 2021

    A React Conf talk by Xuan Huang previewing React Forget, a compiler that automatically memoizes components. It argues for making memoization the default so developers need not write useMemo or useCallback by hand.

    Shared in discussions of useCallback and memoization as the first look at where React was heading with an auto-memoizing compiler.

    Software Engineering & LanguagesWeb developmentCompilers, interpreters & program analysisSoftware performance & optimization
    1. 31:11
      React.js Conf 2015 - Immutable Data and ReactMeta Developers159K views • 11 years ago
    2. 30:41
      Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015ReactEurope472K views • 11 years ago
    3. 13:45
      A 10x faster TypeScriptMicrosoft Developer608K views • 1 year ago
    4. 31:17
      React.js Conf 2015 - Hype!Meta Developers108K views • 11 years ago
    5. 35:32
      Cheng Lou - On the Spectrum of Abstraction at react-europe 2016ReactEurope63K views • 10 years ago
    6. 36:45
      Rich Harris - Rethinking reactivityYou Gotta Love Frontend334K views • 7 years ago
    7. 1:35:30
      React Today and Tomorrow and 90% Cleaner React With HooksReact Conf1.2M views • 8 years ago
    8. 56:23
      Speed Up Your JavaScriptGoogle TechTalks136K views • 17 years ago
    9. 36:31
      Hey Underscore, You're Doing It Wrong!InfoQ141K views • 13 years ago
    10. 25:55
      React.js Conf 2015 - Beyond the DOM: How Netflix plans to enhance your television experienceMeta Developers26K views • 11 years ago
    11. 31:48
      Lin Clark - A Cartoon Intro to Fiber - React Conf 2017Meta Developers216K views • 9 years ago
    12. 24:28
      Sebastian Markbage: Minimal API Surface Area | JSConf EU 2014JSConf71K views • 12 years ago
    13. 35:42
      Progressive Performance (Chrome Dev Summit 2016)Chrome for Developers34K views • 9 years ago
    14. 27:45
      React.js Conf 2016 - Ben Alpert - What Lies AheadMeta Developers50K views • 10 years ago
    15. 44:36
      Hacker Way: Rethinking Web App Development at FacebookMeta Developers900K views • 12 years ago
    16. 29:32
      Pete Hunt: React: Rethinking best practices -- JSConf EUJSConf548K views • 13 years ago
    17. 33:25
      Dan Abramov: Beyond React 16 | JSConf IcelandJSConf139K views • 8 years ago
    18. 59:31
      ClojureScript in the Age of TypeScript — David NolenChariotSolutions29K views • 5 years ago
    19. 25:47
      React.js Conf 2015 - The complementarity of React and Web ComponentsMeta Developers22K views • 11 years ago
    20. 51:18
      Lexical Scanning in Go - Rob PikeGoogleFOSSSydney162K views • 15 years ago

    3 comments from Hacker News

    1. @brundolfAug 2022· in “Not using useCallback is premature optimization”

      For those pushing back, I wanted to share this talk given at a recent React Conf: this video The idea (still just an internal prototype) is that one day your compiler might automatically memoize all React components and intermediate values for you. It obviously would be great to skip all the syntax noise, as well as the linter-enforced rules around correctly maintaining dependency arrays, etc. But I think a big takeaway from this talk is that the React team sees memoizing as the norm . It is something to do by default , so much so that it may happen without your intervention one day. Immutability and value identity-based comparison are core to React. Violating these is the only way memoization can result in bugs (as some in this thread are worried about), and if you aren't following them then a lot of your React code is only working by accident to begin with, memo or no memo.

      RecommendsView on HN
    2. @ksbrooksjrOct 2022· in “Ten Years of TypeScript”

      I agree that the typescript team should consider using the compiler to extend javascript rather than just supplement it with types. Like you said, there are technically parts of typescript that don't have a direct corollary in js (enums/namespaces), so why not take it a step further and add some of the features that js is missing? The only example where they've really taken that next step is with experimental decorators. I think in general the js/ts community is starting to realize that if we're going to have all of these build tools, we might as well use them to do more than just format, transpile, and bundle. Svelte has sort of pushed this idea with its abuse of the js label feature (it can detect when a variable is reassigned if you prefix it with the dollar sign label, which is technically not possible with js, even with proxies). There's also React Forget, which is promising to completely rewrite components at compile-time to avoid all of the gotchas that hooks have (and improve performance) [1]. In terms of making all of ts erasable, you can technically just write all your type definitions using js-doc comments, in which case the compiler can just be run with the --noEmit flag, and then the code is fully valid js without any modifications. [1] this video

      CitesView on HN
    3. @matvpMay 2023· in “Next.js 13.4”

      There isn't much info out there yet, but this video is a small preview: this video The latest update is mentioned in the March 2023 blog post: [LINK]

      CitesView on HN