2 ms·
The interaction with the DOM is what turned me off to D3. The charts, graphs, user interactions, and even the API (aside from the DOM integration) are great.
by austincheney 7y ago
The interaction with the DOM is what turned me off to D3. The charts, graphs, user interactions, and even the API (aside from the DOM integration) are great. D3 tries to force an opinionated declarative abstraction to the DOM on the developer. I don't have any problems interacting with the DOM and don't need a tool like D3 dictating to me how that interaction should work or how to write code/interfaces outside of the graphs/charts it generates.
- mirekrusin 7y agoBut it’s all low level functions so you can use your dom manipulation, right?
- mbostock 7y agoExactly. Here’s a quick example of D3 without joins (and more are in the introduction): https://observablehq.com/@d3/d3-without-joins https://observablehq.com/@d3/d3-without-joins