The whole posting is disengenuous.
"the R9 Fury isn't yet in good shape on the open-source driver"
The card won't be changing to fix this; the driver will have to change to accommodate the card; therefore it is more correct to say "The Open Source driver is not yet in good shape on the R9 Fury". In other words, it's not the hardware's fault that the driver doesn't support it yet.
"AMD's open-source developers haven't yet found the time to implement power management / re-clocking support"
The power management model in Linux is Linux's responsibility, not AMD's. The authors of the Open Source driver are accountable *only* for writing callbacks for the device power management component, and populating the structure. It's my understanding that Linux lacks a uniform model for use by all graphics drivers, in this regard. his is a Linux issue, not an AMD issue.
In general, in a hardware world, you either NDA people, or the Open Source is going to lag the closed source, period. This is because openly manipulating code related to an unreleased hardware product in a publicly accessible source repository, instead of a privately held repository, is tantamount to preannouncing your hardware to competitors. You might as well have the CEO call a press conference, and then shoot themselves in the head in public.
Open Source projects have a secondary problem in that, even if the driver source was developed entirely by engineers within AMD, and released the same day as the hardware was made available, the Open Source projects aren't going to be happy just integrating the code as is. They will insist on peeing on it to make it smell like themselves, just as cats do with new furniture, and this will take time. You can either have closed source, or you can have it integrated later than the release date, but you can not have both.