Re:The origins of Objective-C at PPI/Stepstone and its evolu...
by pjmlp on Sunday June 14, 2020 @10:53AM
(#23518059)
In the Visual Studio tooling way and not having to deal with all COM low level details in name of ISO C++ compliance.
Those of us that eventually migrated to .NET were quite happy with C++/CX for dealing with those APIs that Windows team keeps resisting to expose as .NET APIs, and now that has been taken away from us.
Who cares about dynamic text scaling support when one needs to climb a mountain to actually make use of it?
By the way, this is a feature that is actually supported as Win32 C API, most likely because of hurdles to use it otherwise.
As note, having to deal with WRL was never a consideration for the projects where my voice counted for the technology decisions, too many bad memories from ATL/WTL days.
Also it remains to be seen what C#/WinRT will actually bring into the table.
Really, is it so hard for the Windows team to get some Qt and C++ Builder licenses to understand how to offer productive C++ development tooling for Windows application developers?
Because at the end of the day what happens are adoption failures like how the whole WinRT/UWP story ended up, and if the tooling doesn't get better, it isn't Project Reunion that will save it.
Those of us that eventually migrated to .NET were quite happy with C++/CX for dealing with those APIs that Windows team keeps resisting to expose as .NET APIs, and now that has been taken away from us.
Who cares about dynamic text scaling support when one needs to climb a mountain to actually make use of it?
By the way, this is a feature that is actually supported as Win32 C API, most likely because of hurdles to use it otherwise.
As note, having to deal with WRL was never a consideration for the projects where my voice counted for the technology decisions, too many bad memories from ATL/WTL days.
Also it remains to be seen what C#/WinRT will actually bring into the table.
Really, is it so hard for the Windows team to get some Qt and C++ Builder licenses to understand how to offer productive C++ development tooling for Windows application developers?
Because at the end of the day what happens are adoption failures like how the whole WinRT/UWP story ended up, and if the tooling doesn't get better, it isn't Project Reunion that will save it.