News for hackers. Stuff that matters.
Re:Britecharts: D3.js based charting library of components by welder on Wednesday May 10, 2017 @11:10AM (#14308756)
How does this compare to http://c3js.org/, also a reusable charting library using D3.js?
Re:Britecharts: D3.js based charting library of components by Golodhros on Wednesday May 10, 2017 @01:19PM (#14309860)
That's a great question, and we are preparing a write-up talking about the D3 libraries ecosystem at this moment. There is certainly a good amount of D3 libraries out there, and it could be frustrating to do some research on so many!

Specifically, stacked against C3, Britecharts has a more 'D3-like' API, while C3 is a lot more declarative. This means that on C3, we will render charts by passing large configuration objects, while in Britecharts we strive to use a different API, chaining settings like we do on D3.

Also, C3 hasn't been updated to D3 v4, and we can say it is an inactive project.

Re:Britecharts: D3.js based charting library of components by verbify on Wednesday May 10, 2017 @11:44AM (#14309054)
There's also NVD3 - http://nvd3.org/ - https://github.com/novus/nvd3. And there's a product based off NVD3 called sucrose - http://sucrose.io/ and https://github.com/sugarcrm/sucrose.
Re:Britecharts: D3.js based charting library of components by mshenfield on Wednesday May 10, 2017 @12:35PM (#14309532)
The blog post introducing Britecharts has a good discussion of the difference between it and other reusable charting options: https://www.eventbrite.com/engineering/introducing-britechar....

One other big difference is that Britecharts is compatible with the latest version of D3. D3 V4 underwent a major refactor to increase modularity. NVD3 is actively looking for volunteers to help them get there though - https://github.com/novus/nvd3#do-we-support-d3-v4x.

Disclaimer: I work with the folks who develop Britecharts.

Re:Britecharts: D3.js based charting library of components by mparr4 on Wednesday May 10, 2017 @09:11PM (#14313206)
c3 is decent, but it is no longer maintained and with 675 issues and counting, it's the wrong choice for any new project.

We've had it in production for a couple of years now. The best thing about it was it got us off the ground quickly but at this point I think we've likely sunk more hours into debugging issues and hacking features than it would have cost us to have built it with d3.