I know what you meant, is why i mentioned it.
There will still be optimisations in the Api translation layers etc. but we wont need to see constant driver updates for every game that drops, unless a major bug is picked up etc. or some further optimisation has occurred.
BF4 is a good and bad example overall, it has always had problems. but the issues with low abstraction api's can hopefully be resolved when using WDDM2.0.
Reading some of Johan Andersons tweets kind of pointed the problem at the way WDDM1.1-1.3 got in the way of memory management. But that issue is cleared up with WDDM2.0 in win 10. He even mentioned that mantle would perform far better if coded with win10 and WDDM2.0 as the baseline.
https://twitter.com/repi/status/585556554667163648?lang=en
So in regards to the above, with DX12 and WDDM2.0 we should hopefully not see the issues that BF4 had with mantle.
I am thinking the performance issue with the initial fiji boards (since the 285 only had 2GB of ram) and the fury go back to BF4's memory management problems. Since thief and CiV:BE have no problems in mantle with the fury, since it has enough ram compared to the 285.