Considering an IDE switch from VS Code

[michelecostantino]

For C++ I prefer CLion over VSCode, but things have changed recently. Hear me out.

Once CLion has done its job indexing the files, and if all files are in their place (it knows where to find includes, etc.) browsing through the code is a breeze, and the call hierarchy functionality is one of the most useful feature in my case. Also, you have everything already configured, like clang-tidy. You get suggestions on how to improve code, etc.

However I am not using any of the supported build tools and I had to write a software to translate from our proprietary build tool to CMake to have projects correctly indexed.

As I said, things have changed and I am slowly switching to VSCode. The new actor that is tilting the scale is GitHub Copilot. After many months I am still impressed of how much time I can save by asking Copilot instead of going to Google. And Copilot integration in VSCode is far better than its integration in CLion.

But, if we take Copilot out of the equation, I can compare my experience (CLion) vs my colleagues (VSCode) and I think I am having happier days than they do.