Comment by pjmlp | Hacker News Reader

Comment by pjmlp | Hacker News Reader

Parent Full thread

As mentioned by atombender, COM is the main Windows API in modern Windows.

After the Longhorn collapse, all major ideas that were originally implementated in .NET got redone in COM.

Eventually WinRT doubled down on it, and even if they messed up the whole execution, the main goal of Project Reunion is to bring them into regular Windows, now rebranded as WinUI 3.0/AppSDK.

Parallel to that, many .NET APIs on Windows are COM wrappers at their lowest layer.

Classical Win32 C like APIs, are effectively "stable" since Windows XP

Yes, COM lives on as WinRT and the way Microsoft expose their own APIs, but not many apps are using those APIs and even fewer are exposing their own APIs that way. It's not really clear how many people are writing COM objects outside the Windows team nowadays.

Apps written for Windows are definitely using them, even if using .NET Framework, unless their authors are targeting a Windows XP user experience.

And on Windows making a business out of selling components is still a thing.

Additionally any application that integrates into the OS for file viewers, userspace drivers, shell extensions, or any other OS extension point, needs to implement COM interfaces.

Excel, Word, PowerPoint are COM objects that can be scripted by any language (python, delphi, c++...).

It's a pleasure seeing a template word document being managed and compose by python and then sent to a printer to fill report.

   import win32com.client as win32 
   excel = win32.gencache.EnsureDispatch('Excel.Application') 
   excel.Visible = True

Reply on news.ycombinator.com