That "partly" was worth hundreds of billions of dollars but AMD were cheap/shortsighted enough to hire a few dedicated engineers.
That "partly" was worth hundreds of billions of dollars but AMD were cheap/shortsighted enough to hire a few dedicated engineers.
For various reasons, people flocked to CUDA and other proprietary crap. Then, when that proprietary crap became a money maker, people blamed AMD for not supporting their favourite proprietary crap.
AMD did the right thing and was punished for it. They're still doing the right thing and people still complain that their free full re-implementation of Nvidia's runtime, designed for completely different hardware, isn't good enough.
AMD is not a saint of a company but it's consistently better than Nvidia, every time. Doing the right thing just isn't rewarded and it shows.
On Linux at least you can use Mesa to fix it up. On Windows you're.... out of luck I guess unless someone writes a binarypatch or something?
I wouldn't call it great support, NV "just works"
Citation very much needed.
IME a lot of bugs people attribute to AMD's OpenGL drivers were actually game bugs from developers who only tested on nvidia.
Zero debuginfo-related warnings on any driver (except the usual "buffer location is VIDMEM" spam), NV is fine, intel is fine, my (RDNA) AMD card is fine on both Windows and Linux, user with a Vega 64 isn't fine.
We dug into it together and it literally swaps the colours somewhere, and the user said that it crashes randomly on games (confirmed by others, not one-off HW failure), does the same colourswap or have very glitched rendering.
I guess the only salvation is that people usually play DX games under Windows and the bug didn't happen over DX11. But the same rendering restricted to even standard GL3.3 just got BGRA-swapped.
On Windows you may be right, I haven't had to deal with Windows drivers for a few years now.