When I read the headline it was a mix of WHYYYYYYYY and NOOOOOOO
Really, can't we just leave COM in the 90's?
Win32 is the one left in the 90's.
COM gets regularly new APIs.
Except the one without a bright future is Win32.
Since Vista all major APIs are based on COM.
My point is that for the vast majority of developers this does not matter one bit. The Windows API is not relevant to the work that most developers do today. In the cases where a developer actually needs to interact with Windows there are easier technologies available.
Yeah, if we are talking about web developers I guess.
How do you think those easier technologies are implemented?
Just to give an example, React Native for Windows uses UWP.
As for not being relevant, the software for a platform with 80% market share across desktop and laptops, does not write itself.
I think COM is incomprehensible to most developers today--it certainly is to me, and I maintained a .NET application with COM components for several years! COM is so arcane and verbose.
Why invest hundreds of hours learning something with no clear benefit or future? The documentation introduces COM as:
https://docs.microsoft.com/en-us/windows/win32/com/component...
> COM is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. COM is the foundation technology for Microsoft's OLE (compound documents) and ActiveX (Internet-enabled components) technologies.
What does that even mean? It sounds obsolete.