+1 to CLion. Vim is great for what it is-- if I need to make a small edit or even work on C code it does the job well and is very fast and efficient. But at the end of the day it's not a full blown IDE and as such is missing a graphical debugger and profiler, good configuration for interactively running unit tests, and complex refactoring tools.
CLion is pretty much the best C++ IDE I've found by a mile. Eclipse is so slow and terrible I won't even consider it. Visual Studio is amazing but Windows only and really heavyweight. VSCode, Atom, etc. aren't really "proper" IDEs. Then there's open source contenders like Jucipp which while very fast do lack a lot of the niceties of their paid competitors.
My only gripe with CLion is that it's CMake only. This limits its usefulness for Bazel or Autotools projects.
VSCode gets the look right. Indeed, its look is fantastic. But it doesn't get the feel of vim right at all. My fingers speak vim and they know whether they're talking to vim or something hinky. So after a few days with VSC, I go back. Usually it has to do with ex mode which I power edit in a lot. But I do look at VSC every year or so and it gets better.
The lack of a built-in profiler was a big one for me (though this may have improved recently). I do like using external tools like Intel VTune or Morgan Stanley's XPedite but they're not great for the "quick profiling" you might do to test out various implementations of a function or component.
Maybe that's been added since I used it 1.5 years or so ago though.
CLion is pretty much the best C++ IDE I've found by a mile. Eclipse is so slow and terrible I won't even consider it. Visual Studio is amazing but Windows only and really heavyweight. VSCode, Atom, etc. aren't really "proper" IDEs. Then there's open source contenders like Jucipp which while very fast do lack a lot of the niceties of their paid competitors.
My only gripe with CLion is that it's CMake only. This limits its usefulness for Bazel or Autotools projects.