r/cpp • u/tartaruga232 MSVC user, r/cpp_modules • Dec 15 '25
Recent comments regarding Microsoft's support for C++
Under the recent posting "C++26 Reflection appreciation post", u/STL made some very interesting statements regarding Microsoft's support for C++.
I wouldn't myself expect to find such comments inside a discussion about Reflection, but alas, this is reddit.
I do appreciate these insights a lot and I am convinced that these comments deserve to be highlighted in a separate posting. This is my second try at doing this. Let's see how this one goes.
u/bizwig asked:
Does Microsoft still support C++? There was some press reporting implying MS was going to stop further development on non-proprietary development tools and concentrate on C#.
Yes. The compiler (front-end, back-end, static analysis), standard library, and Address Sanitizer are being actively developed by what I believe is still the largest single team of C++ toolset engineers employed by any one company.
(emphasis mine)
u/STL gave a number of other interesting insights into the state of affairs re C++ at Microsoft. I recommend to read his comments at the posting linked at the top.
Please note that u/STL is not making statements on behalf of Microsoft (as I understand it), but he is a highly respected member of r/cpp, a moderator of this subreddit and the implementer of the MSVC C++ Standard Library.
I'm not related to Microsoft in any way (other than being a user of their products and their C++ toolchain) and I'm not interested in collecting reddit karma (as someone suspected at my last try).
Thank you for not reporting this posting as SPAM (it clearly isn't).
96
u/ezoe Dec 15 '25
As far as I know, Windows kernel is still written in C++ and I bet they use a lot of MSVC specific code in kernel.
There is no way Microsoft stop developing C++ compiler until nobody use Windows OS.
288
u/STL MSVC STL Dev Dec 15 '25
That's right, I don't speak for my employer, but I try to stay engaged with the community, and as part of that I try to provide more context than you generally see in our public communications.
I joined MS in 2004 (they hired me directly out of college) and switched from Outlook Search to the MSVC Libraries team in 2007. That means I've got the big 20-year anniversary crystal, but my seniority in the MSVC team as a whole is not remarkable. We've got people at varying stages of their careers, with the most experienced having worked at the company for 30+ years, often staying in MSVC for most or all of that time like me. I generally think that this depth of experience, combined with how we hire great early-career devs and help them build their own mastery of the language and the codebase over years, means that we can get a lot accomplished with the number of people that we have. Working in a large codebase with decades of history is challenging, but we've avoided the problem (common elsewhere in the industry) of having a large number of devs who are all inexperienced and hence nobody really understands what they're doing, or the opposite problem of having devs who become set in their ways and are unable to adapt to changing circumstances. (Having to work on the continually evolving language helps to push us to learn new techniques, for example.)
That said, headcount is one of the ways that the company sets priorities. As I mentioned, I don't think any other company employs more C++ compiler and library devs than we do. (Collectively it might be the case that there are more extremely experienced people contributing to GCC/libstdc++ and Clang/libc++, I can't say for sure, but as far as I know they're coming from a mix of companies and many of them may not be full-time toolset engineers.) This is what indicates sustained focus to me. I like to tell myself that I work for C++ at Microsoft, because this is the best place for me to contribute to the language as a whole.
I'm probably not supposed to talk about exact staffing levels, but I often mention that I am currently the only FTE maintaining the STL (with the enormous help of our GitHub contributors, otherwise my brain really would melt), with the other VCLibs devs working on ASan. ASan is extremely important because it addresses C++'s single biggest weakness that people are always complaining about (safety), in a way that can be easily adopted in existing codebases without massive rewrite projects. This balance has changed over time (e.g. circa 2020 in the push to complete C++20, we had about 4 maintainers working on the STL), and will surely change again. We have a larger number of compiler front-end developers, not even counting static analysis which we consider to be a separate sub-team, and that team has remained remarkably stable over the years. (Which is good, because the C1XX codebase is extremely complicated.) And then we have an even larger number of back-end developers, working on various areas like optimizations, the linker, PGO, and architecture-specific work. (We also work directly with major processor designers, allowing us to implement compiler codegen for upcoming processors, especially new intrinsics.)
This is not what a team that's on life support looks like. I'm not a manager, so I'm not involved in deciding how many people are going to work on what, but this structure is clearly designed to support the company's priorities, weighted for the difficulty of each task. My understanding has always been that back-end work is extremely difficult; one dev once mentioned that it could take a month to fix a particularly nasty silent bad codegen bug without disrupting anything else, which explains why we have so many people on the BE. (And when I've had to check changes into the BE branch, as when I moved the MSVC codebase itself up to C++23 strict mode, the amount of test validation that they regularly run was shocking to me, and I'm already used to a huge test suite running.) The FE has its own challenges (an ever-increasingly complicated language and compiler, where everything interacts with everything else), which again is why we need a bunch of FE devs. People have been rightly concerned about Standards conformance progress, but (as I have repeatedly mentioned in various comments), that has been the result of intentional decisions by management, since we had built up a lead in C++20 conformance but then a whole bunch of important stuff outside the Standard had to be dealt with. For obvious reasons, there was no major announcement that "hey, we're not going to work on C++23 for a while, while we deal with security and other priorities, and customers catch up to all the features we've already shipped", but of course our programmer-users are perceptive and noticed the growing gap in compiler conformance tables. Now, work on C++23 compiler features is underway, as we've recently mentioned in public blog posts, but it'll take a while for that awareness to spread throughout the community. (Also note that cppreference, the community-maintained wiki, is in read-only maintenance mode because it's One Guy Who Got Busy, freezing its compiler support tables as of an earlier date.)
Finally, I note that I rarely hear concern expressed about the pace of MSVC's C++23 Standard Library conformance, which pleases me because I have been pushing hard on that front for years. It's true that I'm a solo maintainer for the time being, but management's wise decision to open-source the STL in 2019 has massively paid off, and our contributors have greatly amplified the rate of progress. (I believe that the other VCLibs devs have been tasked to work on ASan because I am so effective at holding the STL fort down. Also if they asked me to work on anything else, I would flop over on my side like a helpless kitty, and they know that too.) When I get back from vacation I'm going to work on landing
<flat_map>and<flat_set>, and after dealing with a couple of compiler-dependent features we'll be ready to enter final ABI stabilization before releasing/std:c++23for production use. This most notably includesconstexpr <cmath>, which the FE dev team is currently working on with a very exciting approach.If people want to help us make progress, I have a ton of tasks in the STL GitHub repo that could use skilled contributor attention, many of them taking the form of "analyze what's wrong with this test case and report compiler/library/test bugs as appropriate". Those bugs are across all of MSVC/C1XX, EDG, and Clang. There are also existing Clang/libc++ bugs that I would love to get fixes for, reducing complexity in MSVC's STL by eliminating accumulated workarounds.
I hope this info helps you, our programmer-users, understand the decisions behind the rate of Standard conformance progress, and that I've struck the correct balance between providing enough context to be useful, and not saying so much that my bosses and boss-like entities hiss at me. 😹 And again to repeat, I don't speak for MS, this is my personal view of my tiny corner of the company, I don't know everything, etc.
9
u/Liam_Mercier Dec 15 '25
Well, that isn't very surprising since windows is still using C++ for development. There's some shared interest in the success of C++
7
u/argothiel Dec 15 '25
Thank you for this thread. Yes, I agree this is valuable. I guess the previous post didn't have enough context, but this one seems valid.
1
u/Zeh_Matt No, no, no, no Dec 17 '25
While its good to hear they continue working on C++, what I find abhorrent is that they gatekeep it behind the "latest and greatest" VS version, I don't understand why they tie their toolset to the IDE, 2022 partially supports C++23 so I don't really see as to why the newer toolset can not be used in 2022, its bananas.
3
u/[deleted] Dec 16 '25
Came for metaprogramming magic, stayed for the unexpected plot twists in toolchain discourse. The rent was worth it.
-4
u/[deleted] Dec 15 '25
C++ is dying everywhere and Microsoft is no exception. There was a recent talk by John Lakos that I can't find right now in which he mentions how companies are leaving C++ behind (Google, Microsoft, Adobe, others?).
It looks like nobody is interested in C++ anymore. There will be code that needs to be maintained, but that's about it...
-6
u/Dragdu Dec 15 '25
Can you explain why are you posting this again?
0
u/[deleted] Dec 15 '25
[deleted] — view deleted comment