If the values change at any point and the display is updated, animation is much, much more than eye-candy. It's cognitive reassurance and an affordance that allows the user to more readily understand what is changing and how it's changing.
(source: I did the work equivalent to a master's thesis in grad school on building a tool for visualizing qualitative data)
But they can also be distracting and annoying when used in a context where they add gratuitous motion in random areas. The chart.js homepage is itself an example of how not to use animated graphs. As soon as one graph captures your attention, you're distracted by another one animating in the corner of your eye, so you're discouraged from looking too closely at either.
The page as a whole suffers due to its lack of respect for the reader's attention.
Total power !
//Boolean - Whether to animate the chart
animation : true,It's not so much animation of data into it's final state (which is purely eye candy) but rather animation between states. I.e. you want to show how something changes over time, the suddenly it becomes very useful.
Then again I don't know if it's possible to animate between states. (i.e. from 1990-2010)
//Boolean - Whether we animate the rotation of the Doughnut
animateRotate : true,
Honest question: Is animation really a needed feature for this? The opening animation adds no information value and has the negative effect of making the user think the graphics are actually interactive. I'm sure the animation itself isn't memory/processor intensive but it seems like a really unnecessary feature for a charting library that creates very beautiful, static graphs.
edit: OK everyone, I'm not an idiot: of course you should use animated graphs when showing things to the suits...that's the number one rule of graphic design, I believe :).
I only questioned it here because the OP's focus seems to be on a fairly clean and minimalist library, and the one-time startup animations seems to go against that aesthetic. But no doubt, they do liven up the page.