Simple, C++ is not used for RAD development, thats why there is no real RAD IDE for it. Same is also true for example for Python. Pascal as a language was steered into the RAD direction by borland, it also heavily inspired .Not and Java which is why there are RAD tools available for these languages too.
C is a language developed for one reason, kernel development, which is the pure opposite of RAD, looking at C++, there is QT with the QT-Creator, which tends more into the RAD direction, but as with C, the main niche C++ occupies is not rad development, which is somewhat understandable, because the language design of C++, it's strength and weaknesses, are not so well suited for RAD as for example C# or Pascal. For example, there is no concept of Method pointers in C++, there are only function pointers to this call functions.
The design of a language has profound implications on what it's strength and weaknesses are. C++ has by design some base complexity, so the rapid in RAD is already off the table.
Also C and C++ have a "difficult" relationship with IDEs in general, because of the very different tooling available. With using an IDE you are binding yourself to what this IDE can understand. Now let's say you have a C++ project for Windows, Linux and macOS. For windows you use MSVC++ compiler and the corresponding debugger. On Linux you might use GCC and GDB and for Apple you will use the Apple version of Clang with LLDB.
To handle this clusterfuck of a buildsystem you started of with makefiles but soon realized that this is not enough so you either write a configure script using Bash, generate one using Autoconf, or if you are a little less old fashioned use CMake.
So if you wanted to use an IDE, this IDE needs to be capable of parsing this buildsystem and somehow find out how you configured your project (search paths, defines, etc.) and also make smart changes to this when you configure your project. But as your buildsystem is a literally a turing complete scripting language, this is simply computationally impossible, so long story short, such an IDE can not exist.
So if you have an "IDE" it can't really integrate the most important part of your "Development Environment", i.e. the buildsystem and project configuration. So whats the point of having an IDE. So all you are left with is an editor that is configurable to your C++ project (like using clang-completion and stuff), and this already exists, Emacs, Vim, VSCode, there is nothing an IDE could do better than a good editor for such projects.
That said, there are C++ IDEs, but if you use them everyone in your team needs to use them (because a general buildsystem is of the table) which of course has other implications. License restrictions, personal preferences, and simply cross plattform availability. Visual Studio or XCode are great, but only work on a single machine. CLion is good but is proprietary software.
For Java this is solved by having widespread support for simple and unified buildsystems like maven which are well thought through. And languages like Javascript or Rust have their own management tools like npm or cargo which are shipped with the language environment. Similarly this is for Pascal, there are basically two relevant pascal compilers (Delphi and FPC) with each having one IDE that is the defacto standard for them (Delphi and Lazarus). If you don't have much choice, there is no need for such a clusterfuck like C++ has
When I started using C++ and C, I was using a mac, so what I did was I've imported the project into XCode, and configured the XCOde project as the CMake file configures the project for building on Linux (I actually compiled it on a Linux buildserver). The XCode files where added to the gitignore and everything worked fine, I could use all of XCodes functions. But I've always had to sync up XCode with CMake if any changes where done, and the initial effort is huge. So with the next project I simply decided to only use Vim, now I am using emacs with Spacemacs, and I never regretted that decision to switch from IDEs to simple editors. They are great for C++, and there is no feature that IDEs have that is worth the effort I've had before.
Also there is something to the fact that I can simply download a C++ project, fire up vim or emacs (evan via ssh on a totally different pc) and build it with one simple make (or cmake build).
If I want to contribute to a Java project that doesn't use maven, I first need to get the correct IDE for this, which resulted in at one time, me having 3 Java IDEs installed at once on my machine.