View Single Post
Old 07-20-10, 02:27 PM   #12
Registered User
Join Date: Aug 2008
Posts: 84
Default Re: is the nvidia driver falling behind?

Originally Posted by kRogue View Post
(1) Qt's GL backends are junk. Qt 4.5.x was bad, really bad. Starting in Qt 4.6 there have been significant improvements with the GL2 backend(but not the GL1 backend), but in all honesty the GL2 back end is still junk. The reason: the QPainter API does not map well at all to GL (or for that matter D3D). Additionally, there are a great deal of bits in the implementation that produce ugly render results and are slow (rotated text is particularly guilty here).
Are you referring to the GL backends that are still marked as experimental and which the folks at Qt strongly discourage people from using?

Originally Posted by kRogue View Post
(2) KDE4 uses Qt and some of the way it uses Qt are bad too... Qt advises to not use QtGraphicsProxyWidget, oh but KDE4 does. Naughty.

On another note, that KDE4 is slow, but other desktop environments perform well, is that not a clue that maybe it is Qt and KDE, not the drivers?
Except that the problems only occur on Nvidia drivers, and they are not unique to KDE or Qt (Firefox has been having a lot of the same problems on Nvidia with Linux as KDE/Qt).

Originally Posted by kRogue View Post
1) NVIDIA control panel makes it a breeze to rotate the screen, change resolutions, setup multiple monitors, etc. In fact, I have found it much easier than Windows 7 interface.
Except the windows 7 interface, if I recall correctly, supports user-level settings that are remembers across sessions (as do standard xrandr GUI's in Linux). That means you can set your display configuration for each user independently without administrator access and still have them when you reboot.

Nvidia's settings, on the other hand, are lost on reboot unless you make changes to you Xorg.conf file, and such settings are global and require root access. There is no user-level settings at all.

In fact most distros don't even use an xorg.conf file anymore because usually it is not needed, autodetection combined with user-level controls have made it unnecessary for people using most other drivers. Most other drivers are using standard Linux interfaces, allowing developers to develop a standard set of controls that work with a broad variety of drivers instead of having to have different configuration dialogs or different backends depending on the driver you are using. Whether nvidia-settings and twinview work as well or not is irrelevant (although in my opinion they don't), why can't we just use the same tools everyone else uses?
TheBlackCat is offline   Reply With Quote