Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #15054

K

Kevin Schiener

Personal blog · schiener.ioprogrammingweb

Kevin Schiener's personal blog at schiener.io covers programming and web. Since 2024, 5 different Hacker News readers have linked it 8 times, most often “Sneaky React Memory Leaks: How useCallback and closures can bite you”. The last post was in 2024, but the archive is still widely read.

Visit the blog
8mentions?
5HN people?
2024–2025first – last linked?
Links on Hacker News per year · peak 7 in 2024

Too few sampled comments (1) to say how often HN recommends it.?

Why HN links it

HN readers link Kevin Schiener's posts on React closures as supporting evidence that React has hidden footguns and implicit behaviour, alongside a post on the rules of hooks.

Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Kevin Schiener on Web Development.

Most-linked posts?

  1. Sneaky React Memory Leaks: How useCallback and closures can bite you
    3 people · 3 mentions · first linked 2024-03-03
  2. Sneaky React Memory Leaks: How the React compiler won't save you
    2 people · 2 mentions · first linked 2024-07-07

What Hacker News says?

  1. > It's winning because at the core it's just JavaScript function composition. Except it's not. It has a bunch of footguns and implicit behaviours that make no sense unless you're well-versed in the internals of React. See: https://macwright.com/2024/09/19/the-extra-rules-of-hooks https://www.schiener.io/2024-03-03/react-closures And JSX by itself is already a DSL, which drastically changes how it works based on the…

    Comment linking /2024-03-03/react-closures

    on “React is winning by default and slowing innovation”
  2. Submitted Sneaky React Memory Leaks: How useCallback and closures can bite you as a story · 3 points

    HN discussion
  3. Submitted Chrome, HTML Canvas, and `willReadFrequently` as a story · 2 points

    HN discussion
  4. Submitted Sneaky React Memory Leaks: How the React compiler won't save you as a story · 2 points

    HN discussion
  5. Submitted Sneaky React Memory Leaks: How the React compiler won't save you as a story · 2 points

    HN discussion
  6. Submitted Sneaky React Memory Leaks II: Closures vs. React Query as a story · 2 points

    HN discussion
  7. Submitted Sneaky React Memory Leaks: How useCallback and closures can bite you as a story · 2 points

    HN discussion
  8. Submitted Sneaky React Memory Leaks: How useCallback and closures can bite you as a story · 1 points

    HN discussion

Search all of HN for schiener.io