We can analyze another course of action from companies such as Microsoft. Not saying that is better or worse but showing an alternative in big corporations.
Microsoft launched similar initiatives every time for decades even failing at prior tries. In the UI front they "play" with Silverlight, WFP, Windows Forms, MFC and a lot more. Try and retry.
I also think that these issues are worse when you are dealing with hardware: do they open the codebase to continue playing with the devices? I am on the European side of not only repairing youself but opening "dead" code or somethink like that. It is just an idea.
Microsoft is suffering form the reality that Azure is the OS that matters, WinDev seems to be getting new devs without much background on how Windows used to be, and wiht constrained resources versus anything Azure.
Also note that DevTools is no longer .NET only, rather any language that has tier 1 support on Azure.
Microsoft launched similar initiatives every time for decades even failing at prior tries. In the UI front they "play" with Silverlight, WFP, Windows Forms, MFC and a lot more. Try and retry.
I also think that these issues are worse when you are dealing with hardware: do they open the codebase to continue playing with the devices? I am on the European side of not only repairing youself but opening "dead" code or somethink like that. It is just an idea.