4 ms·
This looks beautiful but it doesn't seem to directly attack the main conceptual barriers that I find people run into with D3. These are: how its API is driven i
by zmmmmm 7y ago
This looks beautiful but it doesn't seem to directly attack the main conceptual barriers that I find people run into with D3. These are: how its API is driven in a declarative functional style rather than imperative, and properly understanding the mapping from data space into the domain/range of the plot. Without getting these concepts right up front it can be really confusing. I would introduce those ideas first right up front before talking about the other parts.
- marble-drink 7y agoYep. There is no point at all knowing anything that is presented here without understanding how the API actually works from a high level. For me it was an "aha" moment when suddenly everything made sense (and I realised how nice d3 actually is). The other big problem with d3 is that you don't get much for free with it. Many people are surprised that you have to draw a bar chart using rectangles. But d3 doesn't "draw graphs", it just maps values from your data into attributes in the DOM. You have to know HTML, SVG, CSS, and, of course, Javascript very well already to have any success with d3.