> Then there is the issue they seem to be shoting into all directions, with GUI frameworks, Web, Blazor, Aspire, to see what sticks.
Can you elaborate on why you believe that? I mean, with GUI frameworks it's pretty obvious MS is placing all their chips on WinUI3, even though they are not deprecating any legacy framework. I mean, their Win32 API is still alive and well, as well as MFC, ATL, etc. WPF still gets some minor updates too here and there.
I have no idea what you mean by web, too. ASP.NET is perhaps one of the better maintained web frameworks around. What exactly do you interptet as a concern?
Blazor is also Microsoft's alternative to JavaScript and it's main value proposition is being able to write webassembly apps using Microsoft technology exclusively. What do you think is replacing this?
Pointing out Aspire is even weirder. It's a containerization framework to help with observability and manage distributed applications. What exactly is the overlap?
I sense a great deal of confusion in your comments. What exactly are you trying to say?
Can you elaborate on why you believe that? I mean, with GUI frameworks it's pretty obvious MS is placing all their chips on WinUI3, even though they are not deprecating any legacy framework. I mean, their Win32 API is still alive and well, as well as MFC, ATL, etc. WPF still gets some minor updates too here and there.
I have no idea what you mean by web, too. ASP.NET is perhaps one of the better maintained web frameworks around. What exactly do you interptet as a concern?
Blazor is also Microsoft's alternative to JavaScript and it's main value proposition is being able to write webassembly apps using Microsoft technology exclusively. What do you think is replacing this?
Pointing out Aspire is even weirder. It's a containerization framework to help with observability and manage distributed applications. What exactly is the overlap?
I sense a great deal of confusion in your comments. What exactly are you trying to say?