Are they not discoverable via the command palette? I find Emacs very helpful here, commands are always prefixed sensibly and you can do fuzzy search on them anyway. You can run 'apropos' if you're really stuck and help is built in to every function. It'll show you bindings if you don't know them and invoke a command directly etc etc. I feel like VSCode has most of this. Besides, they're your key bindings anyway, I think it's worth investing in whatever's ergonomic for you given you'll likely spend a decade or more with an editor. One annoyance I had was that extensions were regularly changing commands and throwing away my bindings though.

I should be clear though, I am not suggesting they strip it to the bone at the expense of other users' tastes. I just hate that I can't do that _myself_ because it's not quite as low level as Emacs.

It's difficult to discover a command with the command palette if you don't already know what they've called it.

I dunno, I'm old. I use directories and folders and hierarchical organization instead of searching when I'm allowed to.

VS Code is offputting enough and different enough in conventions from everything else I use that I don't have a great deal of interest in learning it's idiosyncrasies where they depart from standard UX.

I use the Ctrl + shift + p for everything like that until I learn the shortcut.