One of these days I'll whip up a YT video showcasing some of the things I routinely do with Vim, nine-to-five, that you won't be doing anytime soon with a mouse.
But that's a pointless discussion, really, that's about as old as software: Something that has a steep learning curve is often only really appreciated by those
beyond the learning curve, who have experienced the workflow-as-intended, and even if showcasing it to someone on the other side of the learning curve, he'll usually say "yes but it certainly took you a long time learning that".
Both sides are correct, but sometimes the learning curve is worth it, and sometimes it isn't, and it entirely depends on what you're doing.
To make a point, I am a maintenance system coder. I spend virtually all my time poking around in server / backend code written by other people, cleaning up, finding out, refactoring, that kind of stuff. I wouldn't want to do that in any other editor than Vim, because {reasons}.
Someone who expects to do
new development all day in a given project, possibly including setting up a GUI for the software as well, he'll probably benefit from an IDE more than from the advanced features of Vim.
Chose the right tool for your job, but don't bash on tools that aren't the right ones for your job, because they might be just what somebody else needs.