[p_l]

For the targeted use case, their drivers tended to work just fine.

It was when you went outside said use case that things started getting worse, and you had to wait long time for fixes. Sometimes it was because the changes in XFree/X.Org were effectively fixated on how some other vendors did things (cough intel cough), or involved things that effectively nobody wanted to spend engineering to fix properly (like rebuilding rendering path to be able to handle hybrid graphics properly when hybrid graphics came into world years after critical set of X.Org devs decided to stop any real development into X.Org...).

Vulkan Compute also is nowhere close to feature parity with CUDA, so not sure it would be picked up instead.

[shmerl]

Well, Wayland support was a sore point for Nvidia for a very long time. And it's the prime example of why they don't see Linux as their normal support target. Otherwise they would have worked with upstream a long time ago, instead of just trying to start now.

[p_l]

Wayland wasn't in scope of "use cases actually paying for Linux support" (whether directly or transitively) and I wouldn't be surprised if majority of targeted supported applications don't support running under Wayland. The professional market is only now starting to do its toes into dealing with Wayland and that's mostly because RHEL9 defaults to it.

Also, it's not like Wayland offered a concrete target to support, different approaches of how to actually provide device context to applications were from beginning a "now draw the rest of the owl" thing.

[shmerl]

That's the point. They don't care about Linux users and proper working with upstream despite having pools of money. So I'd avoid them on principle as a Linux user.