Wayland support is a valid point though.
Regardless, nVidia remains at the top of the pile in terms of performance and support on Linux. Especially for high-end 3D applications like Maya, CUDA, etc.
nVidia also has fundamental disagreements about the right graphics architecture for the system with many of the Linux folk. I personally think nVidia's concerns about that are valid.
It's unclear whether GEM, etc. are the right long-term approach.
Just a few of the problems that I have had:
1) In a 2 Monitor setup there is no way to rotate one of the monitors into portrait mode without the other unless you create them as 2 seperate X sessions.
2) Fullscreen almost any OpenGL app/game and it will span across both monitors, which just looks weird.
3) A very odd issue where on my second monitor the fonts will randomly screw up or parts of a window randomly become transparent and I can see the window behind (seems to happen mostly with flash) through it. Only way to fix it is to disable and then re-enable monitor.
Yes, I used to have an ATI card and I can confirm that it had just as many if not more issues.
This is because the games often use a library like SDL to do the windowing. Their idea of opening a window is called "SetVideoMode", so no wonder it goes wrong.
If a software uses X11 windowing in a way that most apps these days do, using extended window manager hints for fullscreen, etc, this problem would not exist. Btw. I use my window manager's full screen feature to do this. It works a whole lot better for games which allow resizing windows (this often excludes SDL-based games because you explicitly have to tell SDL you want a resizable window) than letting the game set full screen mode (usually via some horrible deprecated X11 legacy api).
The nVidia display driver is not perfect either, it doesn't support Xrandr yet, so expect problems with multiple displays (and rotation) until the situation is corrected.
What I would love though would be reliable suspend/resume on an OpenGL 4.2 accelerated notebook.
It's not just about having or not having boot messages, which are still there in framebuffer mode if you want them. In fact, with a graphical console, you can see lots more messages at once, at the perfectly crisp native resolution of your screen, with large fonts if you like.
A major part of the issue is video mode switches causing ugly flickers, with many LCD monitors taking ages to resync and turn the backlight on after a mode change. You can miss a lot of boot messages in those precious seconds. Sometimes my monitor takes so long to sync that I don't even get to see the BIOS screen or GRUB menu.
Meta rant: why do people feel the need to chime in with how much they don't want something when someone else says they do?
What I would love though would be reliable suspend/resume on an OpenGL 4.2 accelerated notebook.
Putting all drivers in the hands of the kernel subsystem maintainers would go a long way toward solving that.
That would be nice.
why do people feel the need to chime in with how much they don't want something when someone else says they do?
In this case, I'll admit I'm not a fan of splash screens in general.
I've been a teeny-tiny bit annoyed over the years at the level of effort I've seen kernel and distro developers put into graphical boot schemes when it seemed to comes at the expense of more basic stuff, like you know, working drivers for things after the boot was complete. But it's their time and energy. If they want to put it into showing a penguin holding a beer that's their business.
To me it's usually a sign of form-over-function, or functions-I-don't-want-over-functions-I-do.
It would be cool to be able to launch an OpenGL app without X though.
Also made it much easier to tell WTF was going on with your system and displayed all those warning messages that I am guessing are just hidden away now unless you happen to look at dmesg.