It does seem to be primarily for quick visualization of common use cases. I was a little disappointed because I've been meaning to do some research in speeding up my d3 visualizations, although this seems really cool none the less.
Yeah I thought it was about performance also. One thing I've never gotten around to was really look at the d3 code and see how renderings are done. Does D3 re-render on every property change? Or does it save all the changes and render once at the end.
A quick glance at D3's source code confirms what I suspected: all it does is call setAttributeNS on the DOM. So the re-rendering isn't really its concern, but the browser's.
As for performance, I believe the focus is on the user's performance, not the computer's.
I'm not convinced this would be faster over my current knowledge of d3 but it's pretty solid and if you want to avoid common pitfalls it might work for you.
Comments
It does seem to be primarily for quick visualization of common use cases. I was a little disappointed because I've been meaning to do some research in speeding up my d3 visualizations, although this seems really cool none the less.
Yeah I thought it was about performance also. One thing I've never gotten around to was really look at the d3 code and see how renderings are done. Does D3 re-render on every property change? Or does it save all the changes and render once at the end.
A quick glance at D3's source code confirms what I suspected: all it does is call setAttributeNS on the DOM. So the re-rendering isn't really its concern, but the browser's.
As for performance, I believe the focus is on the user's performance, not the computer's.
I'm not convinced this would be faster over my current knowledge of d3 but it's pretty solid and if you want to avoid common pitfalls it might work for you.