Notebooks form more of a presentation layer. If a lot of code ends up in a notebook it largely needs to be extracted out and put into a library, where you can unit test it. At least for Scala, a lot of our users will develop JARs that they’ll add to a notebook via
%AddJar, and when they need to reload it they’ll restart the kernel.
I put together this comparison table a couple days ago and shared it on Twitter. Apparently it struck a chord.
To be clear, “fast” is not the end goal. The end goal is to sustainably generate beneficial outcomes. Crap shipped fast is…