I think that's a significant difference, in that the <object> variant of this API has the potential for access to the chart elements for styling and interactivity.
I think that's a significant difference, in that the <object> variant of this API has the potential for access to the chart elements for styling and interactivity.
Having recently rediscovered the non-joy of putting somebody else's javascript on a page (in that case WebRing) I am a bit gun shy of the whole model[0].
I really like the idea of 'server driven charts' for easy web pages and illustration. But I would rather have it be something I could put on an Raspberry Pi in my network so that I didn't have to worry either about the privacy issues or it going away (as Chartserver has been trying to do :-).
[0] Imagine what will happen if placekitten.com gets sold to some porn aggregator.
I can't think of many reasons for building them serverwise.. except for when you don't have access to javascript or you are limited by the power as well.
Additionally, you would be surprised at how much could be accomplished in that department with just CSS.