julia-snail VS jupyterlab-lsp

If you want to dip your toes, I'd maybe try out https://github.com/doomemacs/doomemacs if you like vi style keybindings or https://github.com/seagle0128/.emacs.d or if you want to use something more traditional. Then I'd recommend https://github.com/gcv/julia-snail for the julia side of things.

I personally use julia-snail to use Julia with Emacs but it has less introspection than what you'd find in VSCode. Once you're familiar with that, you can use the Julia Language server with Emacs.

Maybe you can use julia-snail instead? https://github.com/gcv/julia-snail

Ah, looks like you are right and indeed ESS doesn't support python, a shame. As for Julia, I think a package that is shaping up to be interesting and along the same spirit is: https://github.com/gcv/julia-snail

PS: I'm also the author of an Emacs Julia IDE (https://github.com/gcv/julia-snail). Definitely not official. Written primarily for me, but it seems that other people find it useful. I'll leave it to others to judge if it possesses the quality without a name.

Emacs: https://github.com/gcv/julia-snail

I've recently seen JupyterLab LSP that bring the static analysis aspect of LSP to the notebook, and been wondering if there is anything similar that try to bridge a running kernel back into Neovim.

JupyterLab is optimised for handling R, Python and Julia. Code intelligence-wise it requires installing jupyterlab-lsp to get all the best features.

Pylance is really a great LSP in VS Code and it's pretty fast, and Jupyter Lab has an LSP that is also great depending on your use case. VS Code has remote host support for Docker, VMs, etc. depending on what your plans are.