I sympathize with the comments, as a software engineer, this comment from Mike really describes my frustration with Observable's runtime: > Observable notebook

I sympathize with the comments, as a software engineer, this comment from Mike really describes my frustration with Observable's runtime: > Observable notebooks are like spreadsheets, where cells run automatically whenever you edit or values change. That’s not how conventional (imperative) programming languages work, so sadly you can’t simply copy-paste a whole notebook into a vanilla JavaScript application. However, I do think many others will prefer their reactive runtime; so this is by no means a criticism to Observable, they are doing great work. They are just not targeting JS-purists and that might be the right call. As a software engineer, I love D3 but don't want to be stuck with a reactive runtime that is not vanilla JavaScript. I got myself to build https://hal9.ai https://hal9.ai, an integrated environment to do data analysis based of JavaScript. Is not a D3 learning environment but you can certainly use it for that purpose. If someone is interested in providing feedback or helping with D3 examples, please do so at https://github.com/hal9ai/hal9ai https://github.com/hal9ai/hal9ai or shoot me an email at javier at hal9.ai