Declarative APIs in an Imperative World
summary
Explains how Atom integrates React with imperative APIs by showing concrete wrappers: a text-editor component that syncs cursor state via Atom's pub/sub and compositeDisposable, a panel using ReactDOM.createPortal and shouldComponentUpdate, focus solved with ref holders and createRef, and git access via model observer / observed model components that fetch and render loading/error states. Recommends using Context or hooks to avoid prop drilling and emphasizes cleanup, performance tradeoffs, and pragmatic partial declarativity.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:09Declarative programming
- 3:52UI state and React basics
- 7:41Integration strategy
- 10:31Atom editor integration
- 13:28Focus and monads
- 18:10Command registry and Git
- 21:51The context of history
- 25:55Confronting ageism
- 30:08Actionable change and closing
related talks
30mDeclarative by default
50mImperative vs Declarative: Weathering the storm
16mThe Declarative Mindset
40mRethinking UI: Imperative to Declarative
19mFrom Imperative to Declarative: Simplifying JavaScript APIs with React.js
35mAdvanced patterns in building React Components
38mEssential concepts to know when learning Declarative UI
01h 04mWhat makes React different?