C++, Pain Points

There were 16 questions in that category. Respondents were asked to rate the severity of each issue on a scale of: major pain point, minor pain point, or not a significant issue for me. The top 3 reported pain points are: **Managing libraries my application depends on** **Build times** **Setting up a continuous integration pipeline from scratch (automated builds, tests, …)** Just to mention, number 4 on the list is *Managing CMake projects*, which I see as related to the first ones. It is interesting that for C++, notoriously known and criticized by its users as a complex and large language, the major issues seem to be infrastructure ones. There can be reasons for that. ... Let’s look at the top 3 reported pain points in reverse order. ### Nr 3: Setting up a continuous integration pipeline from scratch (automated builds, tests, …) From about 1700 results, 31.35% considered this as major pain, 40.85% as minor pain, and 27.80% as not a significant issue. I am surprised that this topic is rated that high as a pain point. … ### Nr 2: Build times From about 1700 results, 43.34% considered this as major pain, 37.56% as minor pain, and 19.10% as not a significant issue. Build times can indeed be an issue. There are multiple reasons. ... ### Nr 1: Managing libraries my application depends on From about 1700 results, 47.37% considered this as major pain, 35.09% as minor pain, and 17.54% as not a significant issue. Nearly 50% of the respondents consider managing dependencies as a major pain point. That is a lot. Managing dependencies is indeed a problem. Not everyone is Google who can say, ... And for some projects, it can quickly become an expensive mess. So yes, I see managing dependencies in C++ as a major pain point. That was my answer to the survey. And it seems I am not alone in that point of view. … C++, as it is today, may not be able to solve that problem.