r/d3js • u/restricteddata • Mar 26 '23
D3 is going to be made irrelevant by its dependence on Observable
I have taught data visualization to undergrads for many years. I used to enjoy teaching them D3 as one very useful approach to this — it had such a wonderful mixture of power and flexibility. I stopped teaching the class for a few years, and I'm back in it again, and I'm looking into using D3.
And after several days of looking at how it is done now, I've come to the conclusion that it's just not viable. Why? Because of fucking Observable and the fact that every answer, every example, every manual page for how to use any modern version of D3 is entirely tied to what is by all accounts a "toy" manual ecosystem.
Don't get me wrong. I think Observable is pretty neat as a tech product. If I wanted to make a modular system for showing people how to do data viz programming in bite-sized pieces, man, it would be great.
But I don't understand what it gets you beyond that. It is absolutely not something you could deploy in any kind of production mode. You cannot generalize any skills learned in Observable to regular programming. It is a hobby-horse dead-end. I cannot justify teaching my students both how to use Observable and how to use D3 given that Observable will be useful for exactly zero of them.
I've spent the better part of the last hour trying to figure out the best way to do some very basic things in modern versions of D3, and all I can find are Observable tutorials that absolutely do not easily convert to regular Javascript+HTML. And you know what? I'm giving up.
If it's this hard for someone who actually used to program in D3 quite a lot just a few years ago to figure out how to get basic stuff working, it's not going to be worth trying to teach it to someone new.
D3 is a tool. Observable is a toy. If D3 hitches itself to Observable as much as it has been, it will become a toy as well. Other things will appear to do what it does better.
/end frustrated rant