I don't see what's the problem here. Bridgman already stated the method the driver follows; developed following the standards set out by the API, with further tunning and bug fixing done as issues are uncovered. Isn't that how things usually go? Bugs will appear after the fact. Individual programs and application change over time and inevitably something will break and/or not work as intended anymore.
As for (3D) performance, I don't see what the big fuss is about. Fglrx is usually on par with the Windows driver in this regard, with individual applications exhibiting issues here and there (ex. WINE, which is not really a performance issue). The driver is currently going over some significant changes in Composite support, which for the mean time means crappy Compiz/Kwin performance; these issues will eventually be ironed out.
As for (3D) performance, I don't see what the big fuss is about. Fglrx is usually on par with the Windows driver in this regard, with individual applications exhibiting issues here and there (ex. WINE, which is not really a performance issue). The driver is currently going over some significant changes in Composite support, which for the mean time means crappy Compiz/Kwin performance; these issues will eventually be ironed out.
Comment