3 ms·
Dunno for me D3 feels like they are trying to do everything at once resulting in an overly complex and hard-to-learn library. When I look at the examples at th
by sydd 8y ago
Dunno for me D3 feels like they are trying to do everything at once resulting in an overly complex and hard-to-learn library.
When I look at the examples at their page I see stuff that I could make in 2 ways:
- Just write a small program from scratch that visualizes one in a week or 2. It will be small, I will know the ins and outs, so easy to change and will be a ton of fun to write.
- Use D3.js (I dont know this library, but i've used complex charting libraries in the past). Likely it will take more time, not because I am thinking of the interesting parts, I will spend most of my day cursing on StackOverFlow to figure out how to skin that one tricky part of my app.
So in the end I dont really see a good reason to use d3.js unless my full time job is to develop data visualizations.
- wpietri 8y agoI learned (some of) D3 in exactly the fashion the article suggested: find something I want to visualize and make it happen. I thought it was great. I still wouldn't say I've "learned D3", but I didn't have to. I got my goal accomplished in a couple of days, along with a lot of nice bits I didn't intend along the way as I found good things that D3 could do for me. For me it was definitely a "design to tools" approach; I looked at the gallery, found something mostly like what I wanted, and then worked to that. That was fine by me; I wasn't looking for ultimate visual control, but just trying to turn a bunch of data into something mortals could comprehend.