Hi Observable maintainers,
Thanks for building such a great framework.
As an old bl.ocks user to learn D3, however, I found it a bit hard to get used to how observable works, especially at the beginning. Now every D3 example is linked to Observable, so as I try to get used to it, I found that I miss some things bl.ocks provided. Let me describe them in detail.
First, I liked how easy it was in bl.ocks to open a standalone web page that only contains the completed visualization and use the browser console to inspect elements and fiddle things. With Observable, I was hoping such an “open” button could exist as well.
Second, the code in bl.ocks was in the order they are executed, whereas in Observable it’s often the other way around. I found it really confusing to see a completed visualizations on the top but have to read code from bottom up. What’s more frustrating is that sometimes bottom up is not a linear order either. If cell A references cell B, there is no guarantee that A will appear before B (or the other way around). This possibly can be alleviated by providing a “go-to-cell” functionality (if I click on a referenced cell B in A, the page jumps to cell B). But I suspect that’s still not ideal for people who are used to read code in linear order.
In general, I feel it’ll be great if there could be a link to the bl.ocks counterpart of a D3 example, if there is one.