Have you had a look at nvim-dap? It's awesome and I have a much better debugging experience than in VSCode/JetBrains (as it's completely keyboard driven). Have a look: https://youtu.be/SIYt1dopfTc
I am a web developer & my current dev setup involves sway window manager(with vim style bindings), intellij (with IdeaVim), ranger file manager (has vim style bindings), firefox with vim vixen, and of course NeoVim (for editing scripts).
They are all disparate tools, and have their quirks around vim emulation, but overall its a good enough coherent experience that I am quite happy with.
qutebrowser is a keyboard-focused browser with a minimal GUI. Itβs based on Python and PyQt5 and free software, licensed under the GPL.
It was inspired by other browsers/addons like dwb and Vimperator/Pentadactyl.
And it still lacks the ability to run remote containers a-la VSCode, where you can leverage all dependencies to the container itself.
Edit: also showing variable values while hovering with the mouse. Also, I forgot that Dr Racket can show you the call stack graphically connecting different source lines
Showing the actual file and the ability to visually view the call stack and jump back up it is fantastic.
Setting breakpoints with a click or keystroke while viewing in the file is another important aspect.
Having the breakpoints available between runs without adding them to a text file... the list just goes on and on with little quality of life aspects.
Again... with no setup or configuration
There's a ton of plugins for visual debugging.
* visual debugging - cli debugging could simply never come close, not matter how much you love using a keyboard over a mouse
* hyper-powerful refactoring, well beyond what any of these language server plugins currently provide: rename file and have all imports corrected, extract class or function to different file and again have all imports corrected, etc.
* Out of the box using the interpreter or compiler from the docker-compose stack - everyone on the team instantly has an identical development environment
* Attaching the visual debugger to your app running in a docker-compose stack
The list goes on and on.
I would love to feel like the "real developer" trope by using only the terminal tools stitched together by endless config and scripts and whatnot, but the hit to productivity is impossible to justify.
I just want to build software.