Beautiful, only complaint is it's 100kb minified - that's a lot of JS. Would love to know if there is any kind of modularization (if I only need 1 kind of chart can I lose some of the weight?).
Oh dear. 100kb is bad for this sort of thing? Does anyone know if that's a commonly held view?
I've been working on a Canvas library for full-powered diagramming for a year and a half and it currently weighs in at 597kb minified. (private alpha going on right now, so its nearing final size)
It's super awesome and covers an enormous amount of enterprise diagramming needs like customizable nodes, links, layouts, an undo manager, data binding, models, overviews, events, commands, tools, you get the idea.
But do you think people will reject it based on the size? Do you think not having a slimmer version would be a deal breaker?
> Oh dear. 100kb is bad for this sort of thing? Does anyone know if that's a commonly held view?
Not at all. For what you are actually getting 100kb is awesome.
However I like to develop really light pages especially for mobile. It's not even all about download size, mobile browsers can bog down even just parsing and keeping JS in memory.
Just the core of Google Charts if 150kb. 100kb seems light to me and certainly not a deal breaker.
But grandparent question is still a good one, is it possible to slim it down if you just use one chart? Probably a common usage is just to have one or two graphs of the same type on a site.
Well it only matters if it's going to get loaded a bazillion times. I mean, if you're focusing on something that's really good at a small domain, than I don't think you have anything to worry about. People keep optimizing crazily based on the assumption that it's going to be everywhere, which seems to be a bit overly optimistic.
Maintainer here. It is ~30kb gzipped, and is modular but there is no modular build yet. Individual plugins and chart types are not required, which cuts out a lot of the size.
The 100kb minified unzipped is a concern of mine, however. As the library evolves, keeping it trim and trimmer is a goal.
Realistically, a few static PNGs would exceed 100KB in a lot of cases. Any image-heavy page is going to have a few hundred KB of data. I wouldn't hold it against them.
