JS lives where you visualize and explore data, so making it better at processing data would be a big win for workflows. When you use a jupyter notebook the ker

JS lives where you visualize and explore data, so making it better at processing data would be a big win for workflows. When you use a jupyter notebook the kernel wastes a lot of resources on visualization and the support for interactive visualization isn't ideal (copy all your data to json, pass that to a JS library which has to do the work). Take a look at ObservableHQ for an idea of what an interface might look like, then imagine numpy semantics and webGPU on top. As a bonus: run on server or in browser locally would reduce cloud bills because you don't need a whole server to do an exploratory analysis.