3 ms·
> I haven't really heard or seen much usage of it since. I think COM is incomprehensible to most developers today--it certainly is to me, and I maintained a .N
by emddudley 7y ago
> I haven't really heard or seen much usage of it since.
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-object-model--com--portal 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.
- ralphc 7y agoWhen I read the headline it was a mix of WHYYYYYYYY and NOOOOOOO Really, can't we just leave COM in the 90's?
- pjmlp 7y agoWin32 is the one left in the 90's. COM gets regularly new APIs.
- pjmlp 7y agoExcept the one without a bright future is Win32. Since Vista all major APIs are based on COM.
- emddudley 7y agoMy 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.
- pjmlp 7y agoYeah, 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.