You always review large code diffs by comparing them side-by-side? You never need to drop into an IDE to follow the path a branch takes? How do you review large diffs without an IDE, do you remember what every function does in a million-loc codebase?

> to follow the path a branch takes

But vscode and vim do this just as well (in my experience). JetBrains products' advantages over the most lightweight solutions for me are:

- Faster intellisense at least for C# and Java

- Faster syntax errors and other linting-warnings

- Refactor tools

- Debugger and stack state viewer

I still use Rider, but I just don't think faster intellisense/linting matters to me nowadays. Refactor tools feel like something that should come with harnesses. The debugger still helps, but to be honest LLMs are better at debugging than me if you let them dump whatever information they need.

Plus, even with LLMs' help, making and managing a plugin for Rider is a much heavier process than the counterparts for vim/vscode.