Live data from Hacker News

Apache ECharts

echarts.apache.org

231–240 of 263 posts

Re: Apache ECharts

#231

I'll toss some props to `go-echarts` [1], which allows you to declare charts with Golang types and it all gets bound to JSON automagically by Golang's JSON marshaller. I've used it for many projects and whenever there's an issue/PR, the maintainer responds quickly. It's fun to Go-embed JavaScript functions and SQL queries, for this weird blend of data, SQL, Go and Javascript. Here's a Golang example that pulls data f…

Now that’s incredible

Re: Apache ECharts

#232
post #222

I would love it if was possible to download the rendered chart, ideally headless. In peak traffic I would prefer to switch to a pre-rendered version, have the pre-rendered version available encase of an error (i.e. data retrieval), or for users not using JS. After the most minimal Google-foo, I see echarts-python [1] which has not been updated in 9 years. pyecharts [2] is looking pretty well maintained though. Years…

You can easily download a rendered chart by using the chart's getDataURL() function. Then just create a new element in your document and set that element's href to the return from getDataURL() and bob's your uncle.

I need to check that out, thank you!

Re: Apache ECharts

#234
post #55

ECharts is in my opinion the best out there. It surprisingly doesn't come up in a lot of lists or search for charting libraries. I've tried them all: chart.js, google charts, amCharts, Highcharts, ApexCharts. We use it in our tool/library https://docs.chartsql.com/

What about D3js? I know that D3js is low level, but with AI it's pretty easy.

[deleted]

Re: Apache ECharts

#236

If you're looking for a chart library for a web client, I also recommend charts.css. It's a godsend honestly, the concept is way simpler than most charts libraries and can achieve the same thing. Makes it so simple to use the old way, server side rendering, htmx, etc... https://chartscss.org/

The biggest problem with this is that you are representing points in DOM, just like SVG.

If there are a huge number of datapoints, this library will paint itself in the corner.

Re: Apache ECharts

#237
post #158

Noticed it uses HTML5 canvas to render data by default. To screen readers, am I correct in understanding that this is equally accessible as when people share screenshots of text? There is an SVG option that looks identical but it doesn't say when you're supposed to use that, or why canvas exists (and is the default) if SVG would work equally well. Then again, setting an example chart to use SVG rendering (I was looki…

You are asking why Canvas? The answer is simple: Canvas is vastly better performing when given a large amount of datapoints. The difference is not even on the same plane.

Re: Apache ECharts

#238
Over the last 7 years I've built 3 major products that needed charts. Every time I tested most of (at that time) popular solutions. All 3 times eCharts was by far the best option, across all criteria. Incredible library!

Re: Apache ECharts

#239
post #80

Earlier quoted context omitted.

Look, it’s not “bizarre” to point out that Observable has deeply shaped the modern D3 ecosystem. The issue isn’t that the D3 API has changed, it’s that a huge number of learning resources, examples, and docs have been rebaked into Observable’s reactive notebook style, which, for people not using Observable, adds a ton of indirection and mental overhead. You might not notice it if you already know D3 inside and out, b…

"You can use as many italics as you want but I don’t think it’s a wildly bold claim and your counter example is simply silly." I don't understand the relevance of any of this, but I think I've done a fair job outlining my points above. Let me give my best summary: the execution environment used by a library's (example) documentation is independent from learning the API of the library itself. I agree that newcomers to…

> But I'd prefer to have D3 documentation in the form of free, interactive Observable Notebooks rather than to have no documentation at all

This is the core point. Yes of course the existing d3js docs are better than nothing. That isn't the complaint. The complaint is the current docs are significantly worse than older d3js docs that weren't notebook-based.

Re: Apache ECharts

#240
post #152

Earlier quoted context omitted.

Link here, for reference. https://github.com/antvis It seems good, but their docs websites are absolute trash (though they've seemingly gotten somewhat better recently - they were previously completely unusable). e.g https://g6.antv.antgroup.com/ Overall, I think you cant go wrong with Apache.

There's one more thing. Leader of antv is the developer of echarts.

really? how/why?
Post reply on HN