derekperkins

I just noticed when my RSS feed filled up with trucker software posts. http://onstartups.com/all still shows the original posts though.

That does look good if you're already using bootstrap. If you're not, it'd be pretty heavy.

There is a ton of documentation yet, but here's a link to what there is: http://www.chartjs.org/docs/#advanced-usage-writing-new-char...

It certainly isn't to the d3 level yet, but almost everything is exposed and extensible with the new API so you can create most any chart you can think of.

That's a great idea

Haha, I thought that HN was smart enough to hyperlink it for me. Thanks for the help. :)

That's pretty cool.

I only see cpu usage on the homepage which should rarely be open for long. The actual docs don't have the same impact, so I think it should be fine as is. Are you seeing something different?

We're working on adding more comprehensive demos, embedded with CodePen so they can be edited and forked. Until that is done, you can see a number of examples here: https://github.com/chartjs/Chart.js/tree/master/samples

@amelius - those are great suggestions. If you could built it in or even help supply the datasets, we could get that up pretty fast.

That's the next major milestone for the docs. We've discussed it, but didn't want to delay the v2 release for it. We're planning on implementing a user showcase in addition to just a few core demos. We'd love your help if you're able to contribute!

We still need to add it to the docs, but here's a sample from the repo. https://github.com/chartjs/Chart.js/blob/master/samples/bubb...

On the custom side, d3.js has more chart types currently supported, but we've added more with this release and made extending / creating new chart types 100x easier. Previously custom work was much easier with d3, but the gap is now significantly reduced.

1. License: As other commenters have said, it's fully open source and free to use for commercial projects.

2. Canvas vs SVG: For my use case, using SVG for lots of data points really slowed down the DOM. Canvas doesn't have that limitation and is easier to export to images if necessary. SVG is nice because you can use CSS to style things.

It's very fast even with thousands of data points. We were combining it with github.com/crossfilter/crossfilter to do client side filtering and aggregating on hundreds of thousands of rows of data.

One of the Chart.js contributors here. Version 2.0 is a massive overhaul of the underlying library focused on ease of use and extensibility. Hundreds of issues from the 1.x branch have been resolved, making Chart.js even more stable and user friendly than ever! Here are a few of the core changes:

- Github Organization: Moved from github.com/nnnick/Chart.js to our own org, github.com/chartjs/Chart.js, where we hope to continue to grow the awesome community

- Scales: New time axis, log axis and multiple axis support

- Animations galore: Just about everything animates now, from adding/removing datasets, updating data or even changing colors. Based on canvas, animations run at 60fps even with tens of thousands of data points

- Dynamic config: It used to be difficult to interact with a chart after creating it, but now it is as simple as changing the object and calling the update function

- Mixed charts: It is now trivial to put a line on a bar chart or whatever combination floats your boat

- Legends: Now supported for all chart types, they can be placed anywhere on the canvas and support toggling data visibility by default

- Chart types: More charts supported out of the box, including stacked area/bar and bubble charts

- Labels: Built-in chart titles and axis labels make it easy to understand your data

- Responsive and mobile ready: Charts, labels and legends all scale down to accommodate any screen size out of the box, with touch event support

- too much awesomeness to list here

Moving forward, the core team is committed to a faster release cycle. Version 2.1 is slated to come out in the next week with:

- Plugin support: Add optional support for features like zoom/pan (forthcoming) without adding bulk to the core library

- Shared data between charts

We'd love your help, so please join and contribute! We have a very active Slack community that you can join at https://chartjs-slack-automation.herokuapp.com. We'd love to add new chart types and to get the documentation translated, so if you think you can help, we'd love to have you!

One of the Chart.js contributors here. Version 2.0 is a massive overhaul of the underlying library focused on ease of use and extensibility. Hundreds of issues from the 1.x branch have been resolved, making Chart.js even more stable and user friendly than ever! Here are a few of the core changes:

- Github Organization: Moved from github.com/nnnick/Chart.js to our own org, github.com/chartjs/Chart.js, where we hope to continue to grow the awesome community - Scales: New time axis, log axis and multiple axis support - Animations galore: Just about everything animates now, from adding/removing datasets, updating data or even changing colors. Based on canvas, animations run at 60fps even with tens of thousands of data points - Dynamic config: It used to be difficult to interact with a chart after creating it, but now it is as simple as changing the object and calling the update function - Mixed charts: It is now trivial to put a line on a bar chart or whatever combination floats your boat - Legends: Now supported for all chart types, they can be placed anywhere on the canvas and support toggling data visibility by default - Chart types: More charts supported out of the box, including stacked area/bar and bubble charts - Labels: Built-in chart titles and axis labels make it easy to understand your data - Responsive and mobile ready: Charts, labels and legends all scale down to accommodate any screen size out of the box, with touch event support - too much awesomeness to list here

Moving forward, the core team is committed to a faster release cycle. Version 2.1 is slated to come out in the next week with: - Plugin support: Add optional support for features like zoom/pan (forthcoming) without adding bulk to the core library - Shared data between charts

We'd love your help, so please join and contribute! We have a very active Slack community that you can join at https://chartjs-slack-automation.herokuapp.com. We'd love to add new chart types and to get the documentation translated, so if you think you can help, we'd love to have you!

While the points in that article are valid, in practice they don't cause as much trouble as Go trolls think. :)

As for moving from Ruby to Rust or Go, Go is almost guaranteed to be faster for developers to learn. The reason for the complaints in the article is that Go is intentionally simple, and you're seeing many people migrating from dynamic languages to Go for those benefits. The fact that Go has its roots in C will make it immediately understandable to anyone with experience in a C-type language.

My final thought is going to address libraries and widespread acceptance. Regardless of your thoughts about Go as a language, there is no doubt it is here to stay. Underlying major technologies like Docker, it has already seen massive adoption. While initial signs are positive for Rust, you're still betting that it continues to build momentum and doesn't stagnate like Haskell.

Interesting, I hadn't seen that package. Gate does look very similar to Throttler, though it isn't very well documented.

The main difference appears to be that Throttler wants to know the total number of jobs up front and so doesn't need to be told that a new job is starting, where Gate more closely follows the WaitGroup concept of incrementing and decrementing the counters manually.

Group is also interesting, but I don't mind running my own error channels and executing my own routines so that I have a little more control.

This is my first time posting code to Hacker News. I'd love to get any feedback on the quality and usefulness of the code as a package.

Throttler fills the gap between sync.WaitGroup and manually monitoring your goroutines with channels. The API is almost identical to Wait Groups, but it allows you to set a max number of workers that can be running simultaneously. It uses channels internally to block until a job completes by calling Done() or until all jobs have been completed.

See a fully functional example on the playground at http://bit.ly/throttler-docs