These questions were shown only to the developers who chose C++ as one of their three primary programming languages.
It’s great to see migration steadily progressing. I am especially glad to see game developers embracing C++20, and I’m looking forward to support from all game platforms. It will be a challenge for vendors to implement, but I am sure it will be worth it for concepts and ranges alone.
I’m really surprised to see the rate of C++20 adoption. Things are clearly changing. We’re seeing a much faster adoption of new standards than we had in the past.
Always remember that there are users scattered throughout the standards timeline. Surveys like this remind us to write code that works everywhere, not just on the latest standard.
I feel that the [Modules] feature still needs some further development, but I look forward to being proved wrong.
Engineers much prefer writing code to tests for that code, and the time spent writing tests outweighs any real long term benefits.
The ongoing situation with packaging C++ code for third party consumption is reflected here. I look forward to this problem being solved, but I have no optimism for that happening.
I am on record as likening CMake to Stockholm syndrome for C++ engineers. It has become the de facto standard, for better or worse, as demonstrated by the clear lead it holds over its competitors.
In CLion, you can use GCC-based, Clang, MSVC, and IAR compilers. For rare or custom cases, a custom compiler feature allows you to use any arbitrary compiler in CLion.
Python’s ubiquity as a programming language for AI and ML means there are no surprises here. The existence of quality libraries like numpy and pandas makes it an obvious choice. Perhaps they need analogues in the standard library, or we need to sort out the packaging issue.
With only 30% of people avoiding static analysis, I am reasonably confident that open-source code will become increasingly safe and secure.
Small is beautiful in this case. I’m interested to see how precompiled headers, modules, and unity builds interact in the coming year or so.
Thank you for your time!
We hope you found our report useful. Share this report with your friends and colleagues.
Participate in future surveys
The raw data from our DevEco 2022 survey is now available. Download, explore, and glean your own insights!Download
If you have any questions or suggestions, please contact us at email@example.com.