Some people spend the vast majority of their time on their own machine. The gains of convenience can be worth it. And they know enough of the classic tools that it's sufficient in the rare cases when working on another server.
Not everybody is a sysadmin manually logging into lots of independent, heterogeneous servers throughout the day.
Yeah, this is basically what I do. One example: using neovim with bunch of plugins as a daily driver, but whenever I enter a server that doesn't have it nor my settings/plugins, it isn't a huge problem to run vim or even vi, most stuff works the same.
Same goes for a bunch of other tools that have "modern" alternatives but the "classic" ones are already installed/available on most default distribution setups.
Someone might have ssh access, just not you :) VPS' will still be VPSing, even though people tend to go for managed Kubernetes or whatever the kids are doing today. But if you're renting instances/"machines", then you're most likely still using ssh.
Ansible (system management automation) runs over SSH. So do a lot of other useful tools, like git, rsync, most everything from the "CharmBracelet" folks [1], and also anything you can port tunnel, so yeah. SSH is still useful to some of us out here. Personally, I do all my commandline stuff locally and manage remote stuff via SSH through various tools and scripting, so I get mostly the best of both worlds there. :)
Not everybody is a sysadmin manually logging into lots of independent, heterogeneous servers throughout the day.