SolidJS - Reactive JSX
summary
SolidJS claims fine‑grained reactivity where components render once and updates run only the small effects that read changed signals, giving no virtual DOM and near‑vanilla‑JS performance on benchmarks. Code examples use createSignal/createEffect and createMemo, DOM expressions as the runtime, and a scheduler that supports transitions and concurrent updates. A working counter demo proves the model, DOMExpressions is published as the core, and Solid Start exists as an alpha for SSR/routing but is not yet production‑ready.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:36SolidJS
- 2:50Counter
- 5:53Solid vs Reactive
- 8:33Global Stack
- 11:49Nested Effects
- 14:57What are we dealing with
- 16:48Lowlevel abstraction
- 18:49Porting to Solid
- 19:49Learning curve
- 20:56Performance
- 22:08React Beginner
- 22:46Concurrent Rendering
- 24:14Alternative Solution
- 25:29Other State Libraries
- 26:08UI Components
related talks
19mSolidJS: Reactivity Unchained
29mSolidJS for React Developers
51mSolidJS - Getting Started
18mIntro to Solid.js for React Developers (or anyone else)
28mSolid for React Developers
34mRendering Dilemma: Reacting to State Change
17mSupercharging React Performance with JavaScript Signal Optimisation
17mDissecting Reactivity Signals Vs vDOM