D3 and React, Together
summary
Argues that D3 only needs DOM access for transitions axes brushes while everything else is pure data math, so use React for rendering D3 for calculations. Shows working examples: a drag‑and‑drop expense UI that updates state and visuals, a multi‑view debate engagement viz linked by React, and a scrollable Hamilton lyrics explorer. Mentions tooling choices: D3, React, sometimes GreenSock for animation, and gives rough limits: SVG ~3,000 nodes (1,000 with fancy animations) and canvas for tens of thousands.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:01How Should I Use D3 and React Together
- 2:41Brushes
- 5:26Why Why Are We Trying To Use React in D3 Together
- 15:02React Visualization Components
- 15:31Node and Link Graph
- 25:50Questions
- 26:15Would It Be Possible To Make D3 Use React for Rendering or Using 30x Video Um Instead of the Actual 1c
- 27:51How Are You Testing with Live Data in the Limitations in Performance
related talks
32mD3 and React, Together
27mD3 & React
29mThe DOM Wars: React vs d3
53mThe React and D3 ecosystems
23mBattle for the DOM: D3 vs. React
21mData Visualizations with React + D3
26mHooked on D3: Creating Animated Ch(art)s with D3 and React
32mStrategies for organically connecting React Components and D3 Objects