> it requires much more boilerplate code to get stuff done
Depends on the language. In C# it’s straightforward. In C++ yes it could be cumbersome. But that’s a language limitation, C++ lacks async-await so some boilerplate code is required to consume asynchronous APIs.
> good luck trying to compile most existing C/C++ code on UWP
Did that more than once. The largest problem is slightly different CRT, i.e. not all CRT functions are available.
For the language however, C++/CX is merely a syntactic sugar on top of regular C++ compiler that compile your stuff into native code. You can enable/disable “Consume Windows Runtime Extensions (/ZW)” for individual C++ source files inside a single project. The linker will happily link everything together.
Also, if you don’t like C++/CX you don’t even required to use it. You can compile your C/C++ code into a UWP DLL that’s not windows runtime components, but expose C-style API instead. You’ll be able to use that in UWP apps just fine.
Depends on the language. In C# it’s straightforward. In C++ yes it could be cumbersome. But that’s a language limitation, C++ lacks async-await so some boilerplate code is required to consume asynchronous APIs.
> good luck trying to compile most existing C/C++ code on UWP
Did that more than once. The largest problem is slightly different CRT, i.e. not all CRT functions are available.
For the language however, C++/CX is merely a syntactic sugar on top of regular C++ compiler that compile your stuff into native code. You can enable/disable “Consume Windows Runtime Extensions (/ZW)” for individual C++ source files inside a single project. The linker will happily link everything together.
Also, if you don’t like C++/CX you don’t even required to use it. You can compile your C/C++ code into a UWP DLL that’s not windows runtime components, but expose C-style API instead. You’ll be able to use that in UWP apps just fine.