Interestingly, this is the exact same argument Microsoft used to explain why it was a good thing that IE6 rendered horribly broken websites.
Originally Posted by DaemonFC
And to a degree, it is correct - if there is a minor error on the page/shader, why not have the smarts to automatically recognize and correct it.
The downside is that it's then impossible to implement the same hacks across competing software, and websites/shaders get worse and worse until they are completely locked in to a single solution. Just take a look at WINE, and how much effort it is taking them to try and support anything other than NVidia drivers. It's not because the other drivers are buggy, it's because WINE started making a lot of assumptions about how the drivers would work over the years that were never valid but just happened to work on one set of drivers.
and you install the latest xorg-server the moment it is released, right?
Or upgrade when the next distro release comes out?
which is more common?
and which makes more sense to target since it gives you some time and room to plan and test?
That isn't why such things happen.
Originally Posted by smitty3268
Such things happen because there are no test suites developed with the specs. So code has genuine bugs that accept invalid input, but nobody notices because there was no test that said "when you parse this here example invalid input, you should be generating this particular error on this line."
When said test suites exist, compatibility goes way way up for everyone involved, as all implementations both accept everything they should and reject everything they should.
Maybe you should not use wheezy/sid if you don't know how to handle multiarch. In that way Kanotix (or pure squeeze) would be simpler to use...
It was certainly part of what happened with IE, although a good test suite probably would have made it tougher for MS to do a lot of the things they did. For example, they specifically made sure it would render pages correctly if the developer opened a tag but then forgot to close it.
Originally Posted by elanthis
I won't pretend to know whether that holds true of OpenGL or not, but it probably has more to do with lack of a test suite there.
Nice driver. Mouse Stuck issue seems to be fixed with that. However i have watermark on the lower right screen now. which is ofc expected from beta driver. So Far no Problems experienced with the driver
Last edited by xpander; 08-13-2011 at 11:34 AM.
Similar to what energyman said above, be patient. All the problems with the above software and fglrx will be solved in time. KDE 4.7 was released less than a month ago and is not yet supported by fglrx. This support will probably come in October with Kubuntu 11.10. Firefox does not enable WebGL for fglrx until Firefox 6, which is due for release in two days time. fglrx will probably not support Firefox 6 until October (Ubuntu 11.10 or Fedora 16).
Originally Posted by DaemonFC
If you want to run unsupported software, go ahead, but don't complain so loudly. Perhaps you could help with bugfixing instead. And be patient.
"Unsupported"? The whole point of standards like OpenGL is that there doesn't need to be specific "support" for applications. The support is for OpenGL and its specs, not for KDE or Gnome.
Originally Posted by madbiologist
If a driver needs to "support" the newest KDE, then that driver sucks by definition.