If/when Wayland becomes the default for Ubuntu, Nvidia will follow. Can't let them ponder the amount of time it would take to code the missing layers for AMD hardware
If/when Wayland becomes the default for Ubuntu, Nvidia will follow. Can't let them ponder the amount of time it would take to code the missing layers for AMD hardware
As a Fedora user I can understand the reluctance. The recent upgrade to Fedora 26 has given me a ton of gnome crashes which I think are Wayland related. Commentary on Fedora channels tends to be along the lines of "Wayland is great and works for everyone (OK, maybe not those with NVidia cards)".
If Ubuntu has millions of users it may have millions of NVidia users. Putting them onto unstable technology to pressure Nvidia into supporting Wayland wouldn't be a great move.
Therefore I can understand Nvidia's lack of haste. They will support the version/fork that Ubuntu chooses. No point in wasting resources until then.
Of course that would not happen if they opensourced their drivers but I kinda lost hope about that...
Ubuntu is the default distro for gaming, too, and I doubt they will jump until it's well ready, and certainly NOT before nVIdia provides support. It would make no sense.
I sometimes fantasize about hooking up twelve monitors for a wicked game of descent, though.
You're right that we don't use our computer card for our graphics and, as many people pointed out, the computation will wind up running on a headless server. On the other hand, during development, our code will be running on our desktops and will be using the GPUs on the graphics card. I've witnessed a developer's frustration with X11 driver issues cause a project to transition from CUDA to OpenCL.
Granted, he didn't just throw a hissy fit an port the code. Rather, it inspired him to write up a tradeoff analysis of OpenCL versus CUDA that showed that OpenCL offered this specific project significant benefits and that the main selling points of CUDA weren't being used in this instance. He also wound up rage coding a prototype port to OpenCL to go along with the proposal.
The project would have moved eventually, since it was the better engineering decision in this case, but it was about a half decade away on the timeline until the lead dev's compositor stopped work.