I'd be surprised if there is a serious language that doesn't come with at least some semi-official style guide. But usually they are not universally followed and everybody just does their own thing.
Just to add, I’d argue dotnet has one of the best sets of guidance on style. It goes beyond just naming and towards how to structure code for easier consumption and consistency. People love to dump on MSFT, but the dotnet platform is superb.
Highly agree. I’ve been writing code since I was in the single digits and while these days I write mostly Python, Haskell, and C++, I was blown away by the quality of C# and dotNET’s documentation (used it for a few Unity projects) to the point I actually miss it and am considering C# for a Godot project.
I’m not at all a fan of Windows, Office, Azure etc but Microsoft truly got C# right.
It’s important to remember that MSFT is a huge org with a lot of different products. Windows and Office are their own profit centers and have their own strategies that are distinct from DevDiv & Azure.
To summarize the explanations i've come across: It's tailored to Google's internal teams maintaining tons of legacy C++ code, doesn't cover exception handling, and generally has outdated advice best suited for the code they developed in that time period. While their style guide is ideal for maintaining consistency with Google's existing codebase, someone working on a modern C++ project should consider using the language's more modern features and STL components
Something I'd want to note though, someone developing in C++ for an embedded platform or even working on hardware drivers would probably have very lean and mean code which doesn't conform to a particular style guide, especially ones advising against use of "unsafe" operations.