You know that "non-dataframe oriented engineering" is most of physics and engineering, right? It was not a super specific example, it was a standard example of

You know that "non-dataframe oriented engineering" is most of physics and engineering, right? It was not a super specific example, it was a standard example of a plot of a field, a type of data that makes no sense as a dataframe. I know that ggplot is great at what it does but why can you not accept that your work and the tools you like using for your work are a small subset of dataviz? I am sure you are great at your corner of it, but the suggestions you are making are just silly for other types of very common dataviz. And the "inspiration shared by Julia as well" comment is just factually wrong if you are still talking about dataviz libraries. It is *mostly* wrong about the language as a whole. And using JavaScript is a silly suggestion if you want publication quality static plots. And D3 is a ridiculously bad suggestion for engineering plots that is drastically more difficult to use than matplotlib for bespoke engineering visualizations. The reason matplotlib is the library used for the vast majority of physics and engineering journal papers is not simply inertia, it is the ease with which it customizes engineering plots. Most of my work takes 30ish lines in matplotlib (the nicer OO interface), is impossible in ggplot, and would take hundreds of lines in D3. But yes, when I work with data frames, of course I would use something like ggplot, not something like matplotlib.