I'm a huge fan of MinGW-w64, though. I would bet most involved in the issue are. We all win by improving the status quo - I'm just a buffoon figuring out the best way to do that :)
Notably since DirectX headers are always a different case compared to the rest of the Windows SDK
The author of the issue spoke about his troubles with MinGW in four bullet points at the top that are not related to DirectX at all, whether you agree or disagree with those the fact is most people (including Andrew Kelley) rebutted many of his arguments, and Andrew even reached out to MinGW devs on IRC to chat about the topic of contributing upstream. That seems a reasonable approach to me.
I chimed in on the issue because DirectX 12 was the problem _I_ faced, explained what I learned, complained I still don't have a super official way to get up-to-date DirectX headers that are compatible with MinGW, and ultimately said I gave up on working on the issue out of frustration.
Throughout the issue there are people suggesting throwing out all of MinGW would be reckless, heck even I concluded that would not be possible for multiple reasons in my write-up.
I think people are reading too much into the title and trying to make this out to be some sort of attack on MinGW, I really do not think that was anyone's intent - we're just exploring if we can improve the status quo..
The only thing i remember being an issue at some point (and perhaps still is) is that it relies on msvcrt.dll that theoretically isn't part of the Windows platform but in practice that DLL has been there since Windows 98 and the chances of this ever being a real problem are zero - so it is really an "issue" about discussions with hairsplitting pedants than a practical one :-P.