4 ms·
Component object model. It’s a windows thing from the 90’s that still permeates the lower levels of windows programming.
by imron 4y ago
Component object model. It’s a windows thing from the 90’s that still permeates the lower levels of windows programming.
- pjmlp 4y agoNope, it is the way modern Windows APIs are done since Vista.
- imron 4y agoThat doesn’t negate anything I said.
- pjmlp 4y agoThe way you phrased it kind of implies it being legacy and we still need to deal with it.
- imron 4y agoIt kind of is legacy. Yes, lower-level modern APIs are written in it, but you can write a modern windows GUI app without really needing to touch COM directly because there are other abstractions built on those APIs. This was not as true of Windows programming 20 years ago.
- pjmlp 4y agoAs someone that does Windows since version 3.0 I am quite curious what those would be. Forms and WPF? Forms is in maintainance mode, and WPF builds on top of COM via DirectX 9. MFC? Likewise maintainance mode. WinRT and UWP/WinUI 2.0? COM + IInspectable + .NET metadata + AppSandboxing WinUI 3.0? COM + IInspectable + .NET metadata MAUI? Built on top of WinUI 3.0
- imron 4y agoNot sure how this disagrees with my statement that "you can write a modern windows GUI app without really needing to touch COM directly because there are other abstractions built on those APIs"