I have VSCode installed and sometimes I try using it, yet I don't think it will become my main driver anytime soon. First, I couldn't figure out the Leader key

I have VSCode installed and sometimes I try using it, yet I don't think it will become my main driver anytime soon. First, I couldn't figure out the Leader key modality like in Doom and Spacemacs. I found an extension called VSpaceCode - it ain't great, yet not terrible. There's noticeable latency when I move around the file or type, it's a small annoyance, apparently, all Vim plugins for VSCode suffer from that, meh, but whatever. I still need to learn how to extend it, e.g., I don't know how to add some local leader keybindings. Having to use mouse all the time is mildly annoying. As a hardcore Vimmer I abhor such workflow. Opening a file feels wonky, but I probably need to find the right extension or set some settings, not sure. I still can't figure out the simple "find-file" feature where I simply type the filepath, e.g. ~/foo/bar/zap.js and it just gets opened or created. I miss features of Emacs like Hydra or Transient, I'm not sure if there's anything similar - I suppose there some extension for that. I don't know if it's even possible to have indirect buffers. In Emacs, I often open a file, then clone the indirect buffer and work with the same file, in two separate buffers as if they are completely unrelated entities. That allows me to hide/collapse certain portions of the file - great for when I need to focus on a specific function, while also looking at the header or the footer portion of the module. I'm not sure how to completely hide some parts of the file in VSCode, even without cloned buffers. I miss some basic stuff that I got used to. Like for example in Emacs, it's easy to figure out what pressing a key in certain context binds to. There's no `describe-key` functionality in VSCode, you have to open the keyboard shortcuts editor. But if the key is driven by some extension - in my case Vim-emulation, then it gets a bit difficult. I intuitively know that "gd" in Vim's Normal mode is bound to Go-to Definition, but I have no idea where and how this key is set and how to rebind it. Code navigation and autocompletion in VSCode is nice, that's true, it is also true that sometimes it is hard to figure out all the proper steps to replicate same good navigation in Emacs for a specific language. Yet Emacs still offers unmatched extensibility, and it's easy to extend existing packages. afaik there's no equivalent to hooks or advising functions in VSCode, similar to Emacs.