Unless you need to work on a solution with more than a few projects, such as Unity games. Then the LSPs go haywire and eat 20+Gb of memory, while not actually working.

Which, ofc, is Microsoft's fault, since it's their analyzer that has had the bug for years now. Rider didn't have that problem, but it shits itself when you change branches. You can't win :(

For a few files, sure. Idk how I'd use that on the large corporate Java codebase that I usually work with though. Despite all its memory hogging and unnecessary features, IntelliJ also proves remarkably useful when trying to find anything in these mega projects. Features like ctrl + clicking on a method call to get to its definition (even when it is in a different project that I don't have checked out), the refactoring tools, the debugger, etc are absolutely necessary to get anything done.

IIRC vi has been installed, or perhaps tinyvim, then I always go and install vim-gtk

vim fast, IDE slow, I use vim because I'm impatient