
Originally Posted by
MostAwesomeDude
Can't say I'm really surprised. On one hand, fglrx has massive amounts of code. There's spots in our EXA where we have just said, "this could be accelerated, but not without a lot of spaghetti." fglrx is spaghetti.
On the other hand, fglrx has some known weaknesses. The pixmap test is the classic example, although there were a few others that pleasantly surprised me. Their handling of things when a compositor is enabled also sucks; I would bet that their test numbers would go down significantly if a compositor were enabled, although it's entirely possible that they've improved their compositing since then.]