Do you know if the .net team had they authority to make that decision, or did they need the backing from the Azure team to persuade the top leadership?
> Parallel to it, note how Microsoft also plays a role in Python based tooling nowadays.
Yes, I do. I feel MS doesn't even know the distinction between "pragmatic" and "negligent" anymore. The last language they ever should push is that non-typesafe, self undefining, non-optimisable, compute wasting language called Python. I know, shouldn't mention it, programming langues and religion... I am sorry in advance, but I think MS given their PL research accolades should show taste and technical judgement, rather than endless go-with-the-flow pragmatism.
> Do you know if the .net team had they authority to make that decision, or did they need the backing from the Azure team to persuade the top leadership?
It all started with the folks that joined ASP.NET team with a FOSS culture, with Damian Edwards and David Fowley being the driving force of those early .NET Core day, JSON solution format (which ended up being dropped), replacing IIS with Kestrel, and so on. Eventually they got the backing from Scott Hanselmann and Scott Guthrie, both Scotts nowadays enjoy a very high management position.
If you listen to random interviews of them, at known .NET podcasts like .NET Rocks, Coding After Work, Nick Chapsas, and so forth, they often refer the identity crisis of .NET outside Windows and bringing in new generations, as an ongoing issue.
Example, Maddy Montaquilla, the product lead for .NET Aspire, on her Coding After Work interview, from minute 27 until 32:20.
