Re:Embracing Modern C++ Safely, Book Review
by danachow on Tuesday May 31, 2022 @10:00AM
(#31569568)
> So you believe then, that the majority of C++ code written at e.g. Microsoft is not 'modern'?
Maybe some new code is modern - but there is a tremendous legacy code base that can’t possibly be (and Microsoft has released enough open source that you can verify this yourself). Also retrofitting isn’t magic - the boundary between old and new will always cause problems.
Note that while MSRC asserts that, Azure Sphere OS and Azure RTOS only support C (not even C++), and WinUI team likes to boost themselves how much of the underlying COM components are written in C++ (in UWP some of them were .NET Native).
Also Visual C++ team is quite keen in brigging Rust like safety (as much as possible) to their static analysis tooling.
Have you seen WINAPI?
Microsoft coders are, as a rule, notoriously bad, always have been.
Re:Embracing Modern C++ Safely, Book Review
by SuperV1234 on Wednesday June 01, 2022 @08:10AM
(#31580669)
Are you implying that all past and current Microsoft employees are bad coders?
Obviously not. But an enduring large fraction are, and remain. And code there is practically never improved or modernized, only patched onto. It is a cultural thing: there is no perceived value in anything but new bullet-item features.
So you believe then, that the majority of C++ code written at e.g. Microsoft is not 'modern'?
Quote from [1]: "~70% of the vulnerabilities Microsoft assigns a CVE each year continue to be memory safety issues."
[1] https://msrc-blog.microsoft.com/2019/07/16/a-proactive-appro...