[annowiki]

I consider myself quite adept at cli, I can sed, grep, find, vim, and git quite well.

However, what I never found convenient in cli was debugging. I was a print debugger for years until my job convinced me to try PyCharm.

I've always thought the reason I never found a suitable debugger in cli was just because I was either too dumb to figure out integrating something like vimspector, or too lazy to get used to gdb/pdb. Ctrl-f on this article has no mention of the word "debug." I think I'm not the only one that never used a debugger before I tried an IDE. I wonder how many people still feel superior in their CLI-Vim/Emacs-only workflow and are just print debugging.

[jrop]

I use NeoVim for everything except debugging. For that I (frequently) open up VSCode or Chrome to debug (NodeJS). I haven't figured out a good debug workflow for Rust, though, because I hate print debugging.

[yesbabyyes]

I'm similar to you (but with vim instead of neovim - I have to say VSCode with the vim extension is winning me over though).

VSCode with rust-analyzer (edit: and CodeLLDB) provides a very nice environment for Rust development in my experience, including debugging.