The most frustrating part of using Visual Studio Code for me is the hover/scroll behavior for error/warning messages in the code. You have to hover to view the

The most frustrating part of using Visual Studio Code for me is the hover/scroll behavior for error/warning messages in the code. You have to hover to view the error, and usually the message is out of the hover pane viewport at the bottom, below the type/value documentation. This would be fine, except for the fact that once you have scrolled to the bottom of the hover pane, further scroll events are applied to the code itself, so the hover pane scrolls out of focus and disappear. I spend an inordinate amount of time scrolling one notch at a time hoping for a glimpse of an error message. I only have in-depth VS Code experience writing Go with gopls so maybe this is a very niche issue but it’s so frustrating seeing so much wasted effort go into making and using and solving the weird inconsistencies of hover-based UI elements. The inevitable mess of hacky state management is an invented problem - the cursor should only affect state when buttons are pressed. I miss Plan 9.