Apache ECharts
141–150 of 263 posts
Re: Apache ECharts
#142Cannot recommend it enough - absolutely fantastic library, great documentation, zero issues of any impact to us in five years.
My only wish is for the keyboard accessibility ticket[2] to get some love!
Re: Apache ECharts
#143What does this have over Plotly, Chart.js, D3, Bokeh, etc
Re: Apache ECharts
#144Earlier quoted context omitted.
I refuse to use it out of principle that they have intertwined it with observable. All the modern docs for d3 assume you are using observable. So unless you are relying entirely on AI it’s now even harder to grok the documentation. Not sure why this is so contentious. You can search online how many others this impacted as well. All of the modern examples for d3 were rebaked into the observable notebook pattern and it…
There's Plot, which is as standalone as anything[0]. That said, I still find D3 unparalleled in depth and scope. [0]: https://github.com/observablehq/plot
https://github.com/josephg/egwalker-paper/blob/master/diagra...
I didn't try echarts though. I might have to give it a go if its good.
Re: Apache ECharts
#145Earlier 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…
Pre-observable, I used d3 to develop a very complex visualization with real-time updates. It was difficult because d3 has a lot well-thought-out-but-complex concepts, but the docs and examples helped me fully understand how it worked, and the result turned out spectacular. A few years later, I needed to build a simple novel visualization. A major new version of d3 had come out, and all the examples and documentation…
Re: Apache ECharts
#14622.7MB to download the latest release from Github (87.3MB unzipped). That's an insane amount of JS to download and compile (people often complain about React being ~50kb). The default recommended way to use it is `import * as echarts from 'echarts'` which means you are getting the WHOLE thing. Does anyone with experience know how big is it when you pick and choose modules?
Re: Apache ECharts
#147what's the best way to use a JS visualization library like this while using python for data extraction / manipulation in a notebook format (eg. Jupyter notebook, Google Colab, etc.) ?
Re: Apache ECharts
#148How is the Apache project still alive? Who funds them?
Re: Apache ECharts
#149Re: Apache ECharts
#150We've tested almost every visualization library under the sun when building Briefer ( https://briefer.cloud ) and I can confidently say that Apache ECharts is the best. The main issues with other libraries is that they're either: (a) ugly (b) difficult to use (i.e. having to do things imperatively) (c) not flexible enough Apache ECharts solve these 3 problems. It's pretty by default, it allows us to mount/calculate t…