I want to learn D3. I don`t want to learn Observable. Is that ok?

Like others, I came to this thread hoping to find a basic HOWTO for running d3 code inside a simple web page.

Well, you’re wrong. It is a barrier to collaboration, because I won’t start until I know this thing is useful. I’m not convinced it is.

The whole point of having a javascript engine is so that we can use data from our web applications. I’m not interested in a dynamic view of static data, I’m interested in a dynamic view of dynamic data.

Before I do 10 minutes of work learning your new Matlab/Maple/Mathematica/Juypiter workbook engine, which I’m sure is very nice, I want to know if I can make a basic plot inside my web application, and how much work it will take to get there.

I don’t want to learn your software. I want to know if your software is any use to me. The official answer seems to be “No”.

Either give us a basic ‘getting started’ demo in pure HTML/Javascript, or stop calling yourself a library. Every response makes clearer that d3 is not a library, it’s a platform.

2 Likes