That’s why I use vim.
There are few things as satisfying as seeing a cleared full screen putty terminal on a 43” monitor.
Sure, but depends on what you're working on; I like having quick access to console, unit tests (and automatic run every time change is saved for those unit tests affected by the change), unit test coverage, memory profiler, explorer, Application Insights, and a DB connection if it's a quick thing, I'm more productive with my tools quickly at hand and having hints as to types, etc.
I use vim for anything remote on a server, or if just want a quick text editor to edit config stuff, but coding wholly in vim, not really, I'd probably spend too much time getting plugins sorted to what I like, and then I already have VS Code for that (I collapse everything there, ctrl+b, ctrl+`) and even with multi-GB projects on both, they both perform fine enough.

More than enough space for it at 1440p, at 1080p I have to start hiding toolboxes. Would like to go 4k, but then I need to upgrade both home monitors, so will do that once I save up a bit more, spending most of my income on holidays/trips and kitting out apartment.
Would like to make stuff smaller but it keeps resetting itself when I go to work, laptop screen is 1080p and Windows scaling between different resolutions is iffy (actually noticed W11 improved on that, one of the few things that are better), bugging work to get me a new laptop with a 1440p screen at least, 4k preferred, but procurement is wholly separate in a company this size sadly.
And no, I didn't write those unit tests, I have a line there that I don't pass so I don't bother people with smaller screens/make it nicer opening multiple files side by side.