An example of a feature I use very frequently would be find in files. Sublime does sort of have this, but the ergonomics are worlds apart. In VSCode the search

An example of a feature I use very frequently would be find in files. Sublime does sort of have this, but the ergonomics are worlds apart. In VSCode the search gets refined as I type, the results are in a sidepanel and clicking on a result will change the main editor's view to that location in that file. In Sublime I have to first define which files are even subject to the search. There are options to add folders or to search all currently open files, however a bizarre omission of searching all the files in the currently open project, which is what I almost always want and how VSCode works by default. Then I have to type out the search term, which is sometimes needlessly precise - because in VSCode thanks to the incremental search I sometimes already see that there are no results or just a few results when I've typed in only a small prefix of what I was going to. Once the search is done, in Sublime the results are opened as a pseudo-file in a new tab and clicking on a result switches away to a different file tab. It works, sure, but it's very inconvenient for cases where I want to quickly click through a bunch of resulting files to see which is the one I actually wanted. Lots of switching back-and-forth between file tabs, as opposed to VSCode where it's all done in a single view context with the results always visible in the sidepanel. This is especially annoying in Sublime when a search result is in a file that I already have open but is very far from the search result pseudo-file tab. This means that to get back to the search results I can't even just switch the file tab, I need to first scroll through the open files tabs to even find the pseudo-file. So in short, I guess I would describe Sublime's search as a sort of middle point between using grep and VSCode. It's serviceable, but annoying and wastes my time.