IMO at MSFT there's a big cultural disconnect between the old-guard, who are of course senior management, and FOSS-forward teams. The needs of the latter are no

IMO at MSFT there's a big cultural disconnect between the old-guard, who are of course senior management, and FOSS-forward teams. The needs of the latter are not always understood by the former. E.g. the recent HMR debacle with C#. Part of the problem is that it's really hard to explain cultural significance to people outside a given culture, and FOSS is a strong culture, and so is The Microsoft Way, and the two are uneasy roommates right now. I'd say -- politely -- that they are learning by doing, but there are still things to learn/do, and they'd probably say the same. Anecdotal example: Ironically, MSFT's first move after SolarWinds was to ban Linux from its internal network, CorpNet, for over a year, while they figured out how to do InTune for Linux. Most folks didn't seem to notice, but as someone who lives and breathes Linux, it was like having my wings clipped. (Why Linux? Why SolarWinds? I heard everything from "somebody's raspberry pi was ingress" to "zero trust fundamentalism", but I still don't know. We weren't told.) It was awkward that there was not institutional capacity for securing these endpoints sooner.