To start off, I’d like to mention my admiration for the community and team that has made observable what it is today. I and many others, appreciate having a place to chat, and design D3 data visualizations.
However, when i look at observable from the perspective of a project manager, or team leader, or even as an individual that is looking to expand ones knowledge on the subject of data visualization. I struggle to see how any of the examples on this site can be used in a practical way.
Stripping away the observable runtime is time consuming and painful. In business that means dollars wasted, so why would any project manager want to recommend observable as a resource for their team ?
As we all know data visualization, is centered around data, and in today’s age data can be worth more than gold. The common response “You can just embed the notebook in any site” is a moot point, and is not a practical thing to do, among many things, there are just to many security risks.
As a developer, i’m not able to contribute to the community even though i have d3 and dc-js experience. There are just to many extra steps.
I just would like to understand, what the overall scope is. Will we one day see a “import/export vanilla js” function ? OR is observable hoping to replace the status quo and shift the entire D3 developer community to the observable way of doing things ?
In my opinion, without the “import/export vanilla js” feature on the road map, Observable HQ can’t grow to the size it wants to be, and its not the “sharing tool” that myself and so many others want it to be.