Re:Adding ANSI C11 C compiler to D so it can import and comp...
by pjmlp on Monday May 10, 2021 @07:48AM
(#27104897)
> saurik's reply to your comment feels to me like the epitome of the seasoned C/C++ developer _who is able and willing_ to put up with the tooling setup pains that make C/C++ a non-starter to the "average" developer today.
For me the best example I currently have of such attitude is how an internal WinDev group managed to push for getting C++/CX replaced with C++/WinRT without it being production ready.
After 4 years, still no Visual Studio support for IDL files, one has to manually copy/merge generated files into the Visual Studio project, no two way editing with XAML files, we get continuously told that it only will be fixed when ISO C++ gets compile time reflection.
Apparently they feel that is a productive experience and never came close to try out either C++ Builder or QtDesigner.
I guess they were still using raw C to deal with COM to consider this kind of downgrade as something positive.
For me the best example I currently have of such attitude is how an internal WinDev group managed to push for getting C++/CX replaced with C++/WinRT without it being production ready.
After 4 years, still no Visual Studio support for IDL files, one has to manually copy/merge generated files into the Visual Studio project, no two way editing with XAML files, we get continuously told that it only will be fixed when ISO C++ gets compile time reflection.
Apparently they feel that is a productive experience and never came close to try out either C++ Builder or QtDesigner.
I guess they were still using raw C to deal with COM to consider this kind of downgrade as something positive.