Among the most widely used programming languages, C++ has seen the fastest percentage growth in developers over the past several years. Today, there are more C++ developers globally than there were in the #1 language just four years ago.
This growth reflects a broader shift in software systems, not just language preference.
C++ sits at the center of this long-term trend.
C++ continues to grow because it addresses a problem most languages don’t prioritize: How to build systems that combine high-level abstraction with precise control over hardware behavior.
It allows engineers to:
This combination is often described as efficient abstraction, i.e., control over space and time. In practice, systems can achieve deterministic latency, predictable memory usage and consistent performance under load.
It’s also why other languages with similar goals, such as Rust and C, are growing alongside C++.
As systems push against limits of compute capacity, latency, and energy efficiency, these capabilities become more valuable. “Performance per watt” is in sustained long-term demand with no end in sight.
If C++ is growing, why have newer standards taken time to reach production?
C++20 introduced major features, including modules, coroutines and concepts. These capabilities were important advances, but they didn’t have the same broad “everyone will use them” audience as C++11’s features (e.g., “auto”, range-“for”, lambda functions, smart pointers, move semantics, mutexes):
The result was a gap between capability and immediate applicability in production systems. Many teams recognized the value of these features but did not feel the urgency to adopt them quickly.
We expect C++26 to shift that dynamic.
Instead of emphasizing foundational complexity, it focuses on features that are directly applicable for immediate day-to-day use in production environments:
As with C++11, C++26’s key features are immediately useful to most C++ developers to solve the problems they currently face.
Compiler support is also arriving more quickly, signaling a shorter path from standardization to real-world use. GCC has already merged support for reflection and contracts into trunk.
Adoption is driven by demand, not by standards alone.
C++11 saw rapid uptake because it delivered capabilities developers had been waiting for. C++26 is in a similar position. There is already strong interest in:
These are core challenges in maintaining and scaling production systems. Therefore, teams are more likely to push for adoption, rather than passively waiting for it to arrive
C++’s trajectory reflects broad long-term trends in software engineering:
C++ is doing all three, and it continues to evolve along these dimensions, maintaining low-level control while improving how intent and are expressed.
The result is a language that is not just enduring, but evolving in step with the systems it powers.
At Citadel Securities, we actively engage with the C++ community because we believe contribution benefits both the broader developer ecosystem and our firm. We are proud of the role our C++ committee members and colleagues play in helping advance the field.
Among the most widely used programming languages, C++ has seen the fastest percentage growth in developers over the past several years. Today, there are more C++ developers globally than there were in the #1 language just four years ago.
This growth reflects a broader shift in software systems, not just language preference.
C++ sits at the center of this long-term trend.
C++ continues to grow because it addresses a problem most languages don’t prioritize: How to build systems that combine high-level abstraction with precise control over hardware behavior.
It allows engineers to:
This combination is often described as efficient abstraction, i.e., control over space and time. In practice, systems can achieve deterministic latency, predictable memory usage and consistent performance under load.
It’s also why other languages with similar goals, such as Rust and C, are growing alongside C++.
As systems push against limits of compute capacity, latency, and energy efficiency, these capabilities become more valuable. “Performance per watt” is in sustained long-term demand with no end in sight.
If C++ is growing, why have newer standards taken time to reach production?
C++20 introduced major features, including modules, coroutines and concepts. These capabilities were important advances, but they didn’t have the same broad “everyone will use them” audience as C++11’s features (e.g., “auto”, range-“for”, lambda functions, smart pointers, move semantics, mutexes):
The result was a gap between capability and immediate applicability in production systems. Many teams recognized the value of these features but did not feel the urgency to adopt them quickly.
We expect C++26 to shift that dynamic.
Instead of emphasizing foundational complexity, it focuses on features that are directly applicable for immediate day-to-day use in production environments:
As with C++11, C++26’s key features are immediately useful to most C++ developers to solve the problems they currently face.
Compiler support is also arriving more quickly, signaling a shorter path from standardization to real-world use. GCC has already merged support for reflection and contracts into trunk.
Adoption is driven by demand, not by standards alone.
C++11 saw rapid uptake because it delivered capabilities developers had been waiting for. C++26 is in a similar position. There is already strong interest in:
These are core challenges in maintaining and scaling production systems. Therefore, teams are more likely to push for adoption, rather than passively waiting for it to arrive
C++’s trajectory reflects broad long-term trends in software engineering:
C++ is doing all three, and it continues to evolve along these dimensions, maintaining low-level control while improving how intent and are expressed.
The result is a language that is not just enduring, but evolving in step with the systems it powers.
At Citadel Securities, we actively engage with the C++ community because we believe contribution benefits both the broader developer ecosystem and our firm. We are proud of the role our C++ committee members and colleagues play in helping advance the field.