Microsoft is a many headed beast.
Finding the right contact even for employees inside the beast is challenging and a skill all its own.
Finding the right contact even for employees inside the beast is challenging and a skill all its own.
They'll gladly harvest your data whether you like them or not!
Ha, as if the situation with macOS is much better? The OS space is a (lopsided) duopoly, both Microsoft and Apple know it and have pulled down their sleeves long ago.
They're both crap, Apple is less crap.
This post typed on a macbook pro.
I would describe myself via metaphor: the redneck who likes to race cars, and doesn't care about the car as long as it has most of its wheels, and he'll drive the hell out of it.
I was simply stating fact, without any particular opinions on the matter of fault.
But that is way more normal for microsoft, because it's about redundant products that get merged eventually. What's not typical is internal dependencies being exposed, the case above were many MSFT teams/products in the same tier, the case in this article is many MSFT teams/products in a single vertical, at different tiers of the supply chain.
It's possible that this is more a feature of open source, this being an open source MSFT product (.NET core) and the report having been filed through an open source channel (github issues). I think that if the issue were submitted to some account manager or customer service rep through a channel linked to a paying customer account, the response would have been very different.
But you cannot expect a quality customer service response if there's no $ being paid to the maintainers. Whether it be Microsoft or whatever FOSS project.