Hacker News Reader

What is it about D3 that is hard to explain? I know that documentation is hard, but e.g. something about React makes it easily grokable, and something about D3 is the opposite. Do react and d3 compliment each other? Or overlap?

View on HN

I think the rendering pipeline for D3 is actually the hard/strange part, and to be honest, the less-valuable part too (can be swapped with React). The rest of the API is great. The new strange, unordered observablehq examples with extra DSL interspersed aren't helping.

I agree a LOT with the comment below.

D3.js comes with function that modify the DOM. This is react job too. So using both together can be a challenge.

Reply on news.ycombinator.com