Update Cycle & Reconciliation
How a described output becomes committed host nodes: when an update runs, how the runtime finds what changed, and how it applies it. Most UI performance and list bugs live in this pipeline.
on this pageshowhide
explore
- Templates vs Render Functions6 questions
- Scheduling, Batching & Purity5 questions
- Minimal-Change Strategies5 questions
- Keys & Instance Identity5 questions
- Commit & Host Output6 questions
- Error Boundaries & Recovery6 questions
questions
page 2 of 2Across many teams, some list primitives warn on a missing key and others map by position silently; how do you prevent identity bugs?
basics
~20 sTreat item identity as a data contract, not a review habit: collections carry a stable id, shared list helpers require an identity function, automated checks ratchet violations down, and one test per stateful list asserts state follows the item.
For a long-lived shared component library, how would you reason about choosing a template-based or render-function-based authoring model?
basics
~20 sDecide from the shape of the output the library produces, not from taste: declarative markup rewards a template's analysis and diagnostics, while computed structure needs a function. Then design the escape hatch deliberately and police it.
When is a runtime that ranks urgent updates above deferred work, and can abandon a half-done pass, worth adopting?
basics
~20 sWhen measurement shows an interaction losing the main thread to a heavy update. Ranking finishes the urgent pass first and abandons stale deferred work, at the price of repeated passes, strict purity, and harder reasoning about what ran.
showing 31–33 of 33