Am I the only one who finds the vscode quick file search very very poor? Ctrl p and finding a file on a massive code base takes forever in vscode whereas its 1

Am I the only one who finds the vscode quick file search very very poor? Ctrl p and finding a file on a massive code base takes forever in vscode whereas its 100ms in sublime. Vscode also seems to need to recache the file names each startup. When using sshfs or similar to mount a remote fs to work on and have the file name search play nice is also in an unusable state. Using the remote's linters, git, etc would also be great.. But non existant. Easy enough to ssh in the inline term, but that's not integrated for the plugins etc to pass thru. The file search really sounds like it should be easy enough to self fix. (so can partial search a path, parts of a name and all that factors for a refined search return.. As well as caching those result sets more persistently.) What might be a good way to create a nice lookup behaving like below. (rtree hashmap knearest? Just a rb tree?? Idk) *Eg fs contains 10k files* Project root =/home/user/ *all return top 20 of returned set / returns 10k files /proj1 returns 5k /proj1 .js returns 100 /proj1 ab .Js returns 4 /proj1 abc.js returns 1 /proj1 ab.js returns 1 /p2/js/ab.js returns 1 /js ab.js returns 2 ... Eg. Ab.js is in the subset of /proj1/js/test/ AND /js (that looks in /p2/js + /proj1/js) Anyone working on this or with solutions to any of these issues, I'd be keen to hear from you...