Apache ECharts • Hacker News Board

Re: Apache ECharts

#261

Post by gaws » Sat, Apr 12, 2025, 3:55 PM UTC

the_real_cher wrote: post #225

infecto wrote: post #70

Earlier 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…

When did Observable get their hands on D3? Last time I looked at D3 a half decade or so ago I thought it was an open source lib?

> When did Observable get their hands on D3?

Observable and D3 were created by the same person.

Re: Apache ECharts

#262

Post by gaws » Sat, Apr 12, 2025, 3:57 PM UTC

infecto wrote: post #80

jwilber wrote: post #76

Earlier quoted context omitted.

This is a very bizarre take. If you want to just blindly copy and paste d3 code, you may have issues with the docs being hosted on observable. But absolutely zero part of the d3 api (or core design patterns of use) have anything to do with observable. It’s like saying, “I refuse to use PyTorch because their docs are built with mkdocs.” Moreover, even if the coupling were limiting (which, again, it is not), it’s odd t…

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

Wait. This is actually hilarious.

Re: Apache ECharts

#263

Post by gaws » Sat, Apr 12, 2025, 3:58 PM UTC

mkl wrote: post #121

jwilber wrote: post #76

Earlier quoted context omitted.

This is a very bizarre take. If you want to just blindly copy and paste d3 code, you may have issues with the docs being hosted on observable. But absolutely zero part of the d3 api (or core design patterns of use) have anything to do with observable. It’s like saying, “I refuse to use PyTorch because their docs are built with mkdocs.” Moreover, even if the coupling were limiting (which, again, it is not), it’s odd t…

> it’s odd to attack observable since everything they put out is fully open-source Really? They've finally open-sourced the notebook editor? I can't find it on their GitHub. The long-proprietary notebook editor is a big part of people's objections to Observable.

> They've finally open-sourced the notebook editor?

They didn't because it's literally their core business.