Discover · convex.dev

No picture published by convex.dev

Managing Reactivity with useBufferedState

Stack convex.dev

This is what was read here when it was published. convex.dev no longer carries it in what it publishes now.

Reactivity has taken a dominant position today within web app development. Our components and app state are all reactive, and the world has adapted–most would argue, for the better. But has Convex gone too far? 😉 A new generation of serverless backends like Convex is recklessly spreading reactivity across our databases, server-side functions, and protocols, making global reactivity a new phenomenon. Shared global data is becoming reactive by default. Is this good for the world? In this video, Jamie Turner explores one circumstance where this pervasive reactivity poses a challenge, and he builds one useful abstraction for taming over-reactivity and turning it back into a strength.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from Stack

  1. Convex Auth v2 is finally hereconvex.dev
  2. I asked Convex's CTO 34 spicy questionsconvex.dev
  3. I tried Expo's new Exact with Convexconvex.dev
  4. I built a better Claude Code and Codex appconvex.dev
  5. I built a component to make high frequency updates work on Convex (kinda)convex.dev
  6. Turns out database backups are NOT trivialconvex.dev