4 ms·

COM and Windows Runtime (WinRT) provide standardized ABIs across multiple languages. With the WinRT language projections, it's just like writing 'normal' code.

• pjmlp 5y ago
  And with C++/WinRT you even get back the experience of how it was like to do ATL development.
  • legalcorrection 5y ago
    So I gather that, much more than previous COM projections and templating libraries, C++/WinRT is much nicer to work with. And you can target the WinRT ABI with Rust, .NET (C#, F#, etc.), Python, and JS too.
    • pjmlp 5y ago
      I completely disagree, C++/CX was the best that Microsoft ever had closer to C++ Builder and they killed with their office politics. On top of that, the C++/WinRT folks are adamant to push their east const preference into every Microsoft customer. If you enjoy editing IDL files without tooling support and merging generated files by hand, please do.
      • asveikau 5y ago
        I really didn't like C++/CX from the perspective of the fact that it added weird stuff to the existing syntax of the language, and it had no other compiler onboard other than Microsoft. These two probably killed it more than "office politics".
        • pjmlp 5y ago
          It is a framework for doing Windows development on Visual Studio, follows the same syntax as C++/CLI, in use since 2003, it doesn't matter if anyone else is on board. Even today no other compiler can fit into WinUI/UWP workflows no matter what, unless one is willing to do lots of under the hood workarounds. Office politics driven by people without any consideration for paying customers.