descender wrote on Mar 11, 2017, 11:40:
It's clearly AMD's fault for not getting the OS support inline before launching their fucked up product. It's clearly not MS's fault that AMD released hardware that doesn't fucking work right. At no point could AMD have ever thought they were getting the full performance of their new CPU when they released it to reviewers.
Maybe it's time for some introspective, why are you so willing to make excuses for AMD for fucking this up? We all want better competition in the CPU market, but MS isn't your personal punching bag just because you want something to be true..
you are naively assuming that MS would jump to attention and immediately address these concerns from AMD, precisely adhering to AMDs timetable, or responding in a reasonable way... but in the world of corporate industrialization, it doesnt work like that.
AMD may have a certain need to release this product now, but MS is in no way obligated to enable them to meet this specific deadline... its quite possible AMD told MS about this issue and MS said "yeh yeh we'll get right on that... eventually" and AMD was forced (by their own timetable) to release this product before MS was ready to fully support it
these kinds of back end dealings arent going to be public, for good reason.. namely the "optics" (lol)