People who are interest in this should seriously consider Emacs's org-mode.

Yeah! Org babel makes integrating analysis in a transparent way that follows existing org mode workflows / patterns.

There is an important feature Jupyter has that org doesn’t share: collaboration. If everyone I need to collaborate with already uses emacs and org, great—but that’s a pretty big “if,” I and haven’t seen that opportunity in the wild.

On the other hand, jupyter notebooks may have a garbage format (JSON blobs with embedded b64? Ugh!), and the browser-driven UI sucks (IMO, as an ardent emacser), but they’re ubiquitous and the lingua franca for Python data science. Most everyone you meet is familiar with them and can incorporate them into their workflow, and there’s benefit to the direct rendering pipeline to standalone HTML in a conventional format.

There is actually a viable jupyter interface in emacs, EIN [1]. I’ve used it a lot and it works seamlessly, and reduces the pain of using jupyter by letting me edit within emacs. There are also VS Code plugins that enable jupyter development…

Tldr jupyter can be ugly but it’s widespread and that alone makes org mode Babel analysis a nonstarter for collaboration, but at least there are ways to run jupyter within emacs

[1] EIN == Emacs iPython Notebook https://github.com/millejoh/emacs-ipython-notebook