I stuck with flot but if I was to do it again I would give high charts another look.
Ask HN: What charts javascript library to use?
11–20 of 67 posts
Re: Ask HN: What charts javascript library to use?
#12At New Relic, we use HighCharts ( http://highcharts.com/ ). We constantly get questions from our customers about which library we use, because they like the way they look and function. Highly recommended.
Oh and I did this because i was bored: http://zestmonkey.com/charts.php
Re: Ask HN: What charts javascript library to use?
#13Re: Ask HN: What charts javascript library to use?
#14demos: http://thejit.org/demos/
Re: Ask HN: What charts javascript library to use?
#15Re: Ask HN: What charts javascript library to use?
#16Flot is worth a shot. There may be a python library to generate is server side. When I looked into it, I kept going back and forth between javascript charts vs images. I ended up going with images because I didn't really need dynamic charts. There were also features missing from many. IIRC, Flot couldn't add a title to the x/y axis at the time I was looking at it.
Re: Ask HN: What charts javascript library to use?
#17We use the Google Charts API - it's free and very good. But I haven't seen many others comment about it. Is there a problem with using that?
Re: Ask HN: What charts javascript library to use?
#18Re: Ask HN: What charts javascript library to use?
#19This one is pretty fun: http://danvk.org/dygraphs/ - the best part IMO is that the charts are interactive.
Re: Ask HN: What charts javascript library to use?
#20IMO, candlestick charts are way underutilized. Take application response time graphs for example. Most reporting suites rely on moving averages. If your application can have an acceptable average response time, but still have a high level of deviation. Let's say you have an app where, on average, one out of six requests is an entire order of magnitude slower than other requests:
# Ruby code where r is response in ms
r = [
100,
100,
100,
100,
100,
1000
]
r.inject{ |sum, ms| sum + ms }.to_f / r.size # => 250
So my average response time is 250ms, which I may consider acceptable, yet some responses are taking 1000ms, which I wouldn't consider acceptable. With a simple line chart, I wouldn't see the significant deviation. With a chandlestick chart, the upper boundary would be blindinly obvious.