Considering for the umptienth time whether to try #vscodium, in order to start using Julia.
Pro: It seems to be the only "full" IDE for #julialang in active development (since MS bought Github, development on #Junolab, an Atom extension, was stopped), and other than that, there's only text editor extensions for syntax highlighting and such, but no built-in debugging etc.
Con: If Vscodium becomes the only thing everyone uses, MS has the power to ruin it all...
@Mr_Teatime
With you on this. I reluctantly use #vscodium to explore new Julia projects - but it's still less than half my Julia dev that happens in VSCodium. Neovim has LSP support and is not a bad Julia editor, and pretty much everything in VSCodium you can do from the cmdline REPL itself, it's just about the polish and ease of use.
@digital_carver
I was completely spoiled by Spyder and Pycharm, while learning Python.
Now I never want to let go of the ability to have docstrings show up whenever I start typing a function call, autocomplete from the kocal namespace, send any selected piece of code to a console, view the contents of variables in separate windows while debugging, see the call stack, graphical profiler ...
Maybe I'll try Juno, if it's srill usable, and hope for something to replace it...