How to deal with the choice of development environment after a year of work in C ++ Builder?

Question

Java

I have been programming with C++Builder for about a year. The choice of development environment was not made by me. I now deeply regret that I wasted a whole year on this Wednesday. VLC errors are astounding. Solving bugs at times becomes simply impossible.
Question for senior level developers. I want to change my development environment. How to make the transition from C++ Builder as painless as possible!

Answer 1

Question for senior level developers.

Why? You and junior can answer, because the question is at the trainee level.

How to make the transition from C++ Builder as painless as possible!

Don't think of it as a transition. Think like learning a new technology.

Answer 2

How to make the transition from C++ Builder as painless as possible!

If you really have the time and desire, then try to work with a "naked" stack. Assembly - shell script, editing in a general purpose editor. Then you can choose the compiler and editor separately.
Which compiler to choose is a separate question, it depends on the platform you are used to and your goals in terms of learning the technology. You can, for example, Klang try.
When you put it all together yourself, you can try CMake - the tool is not easy, sometimes even confused, but it will not let you relax and will be a good investment of time if you are going to do C ++. At the same time, you can decide on your preferences in terms of employment and the platform on which you want to work.
The IDE will become just one of the tools for you, and this issue will worry you last.

Answer 3

Visual Studio or CLion. But why is the question with Java and C# tags still? It seems that by changing the development environment you meant something more than changing the IDE. And what kind of painful transition can be with the change of IDE?