3 ms·
I think it's just a balancing of where work is needed. C++/Cx (and it's predecessors) was bad in requiring special compiler support whilst WinRT had already se
by whizzter 4y ago
I think it's just a balancing of where work is needed.
C++/Cx (and it's predecessors) was bad in requiring special compiler support whilst WinRT had already seen real adoption and cppwin32 didn't really give any benefits apart from another backend so they seem to have concluded that C++ devs would easier be supported by something more mature (that needed support anyhow) and then just focus the win32metadata project (That's still alive) on "new" languages.
- pjmlp 4y agoAdoption by WinDev, nobody else cares after they screwed their customers. They should all have been fired if it was up to me, we don't pay VS licenses for killing our workflows like that. WinRT is Windows only technology, who cares about extensions. Plenty of people don't have any issues with GCC and clang extensions, or macOS specific ones like Objective-C++, or TI, or ARM SDK, or whatever fancies their party, only MS ones are bad.