True! I remember "upgrading" from ipython as a terminal REPL to ipython notebooks when it was a shiny new thing. Since though, I've more or less joined the an

True! I remember "upgrading" from ipython as a terminal REPL to ipython notebooks when it was a shiny new thing. Since though, I've more or less joined the anti-notebook camp and use the ipython REPL almost exclusively. My workflow, interestingly, is a callback to how MatLab, R-Studio, Spyder (and probably other IDEs, especially those catered to data or scientific work) traditionally facilitate work, which is to edit source along with a REPL and some interactions between source code and the REPL for some sort of quasi REPL driven development. With ipython as a REPL, and the ability to just dump code from source into the REPL, I find notebooks way too bloated for most needs while providing the niceties of an actual text editor or IDE with all the normal linting etc that jupyter are struggling to provide last I checked. As you imply, it's a bit of a shame. Ipython (REPL) and the kernel interface are probably the best parts of the jupyter ecosystem.