I would say the copilot system isn't really there yet for these kinds of changes, you don't have to run experiments on a language framework to figure that out.
Now you don’t even need the frustrated end user!
The answer is probably that the Copilot team is using the rest of the engineering organization as testers. Great for the Copilot team, frustrating for everyone else.
Anyway, this is his public, stated opinion on this: https://github.com/dotnet/runtime/pull/115762#issuecomment-2...
They only gave their customers 9 months to migrate away.
I'm expecting that Microsoft did this to artificially pump up their AI usage numbers for next year by forcibly removing non-AI alternatives.
This only one example in AdTech but I expect other industries to be hit as well.
For it to be "failed" it would have to also be finished/completed. They are likely continuously making tweaks, this thing was just released.
I recently spent a couple of months studying C# and .NET and working on my first project with it.
.NET, Blazor, etc are not known for a fast release schedule... but if things are going to become even slower with this AI crap I wonder if I made the right call.
I'm quite happy how things are today for making web APIs but I wish Blazor and other frameworks were in a much better shape.
I am genuinely curious though to see the strategies they employ to absolve themselves of guilt and foolishness.
Is there precedent for the entire exec and management class embracing a new trend to this kind of extent, then it blowing up in their faces?
Eg:
Minimal APIs were released in 2021 but it won't be until .NET 10 that they will have validation. Amazing that validation was not a day one priority for an API. I'm not certain if even in .NET 10 Minimal APIs will have full parity of features with MVC.
Minification of static assets didn't come until .NET 9 released in 2024. This was already commonplace in the JS world a decade earlier. It could have been a quick win so long ago for .NET web apps.
Blazor was released in 2018. 7 years later they still haven't fixed plenty of circuit reconnection issues. They are working on it but progress is also quite slow. Supposedly with .NET 10 session state will be able to be persist etc but it remains to be seen.
OpenAPI is also hit and miss. Spec v3.1 released in 2021 is still not supported. Supposedly it will come with .NET 10.
Not from .NET but they have a project called Kiota for generating clients from OpenAPI specs. It's unusable because of this huge issue that makes all properties in a type nullable. It's been open since 2023. [1]
Etc.
"It would have to be finished/completed"
Do you honestly not see a problem with those two statements in such close proximity? Is it finished or is it released? The former is supposed to be a prerequisite for the latter.
We can debate whether they should have called this an experiment or an alpha or beta or whatever, but that's a different discussion.
The fact that people are using it currently does not make it a failure. When MS shuts it down, or Copilot is wildly unprofitable for multiple quarters, team behind it quits, etc, etc, then we can determine whether it has failed or not.
But if they continue to have paying customers and users are finding some benefits over not having Copilot, and MS continues to improve it (doesn't let it rot), then you'd have to provide some evidence of its failure that isn't "look at Copilot being stupid sometimes". Especially when stupidity is expected of it.