3 ms·

> Just look at how many projects are using Linux and cuda and don't support AMD. That's because of the CUDA api specifically. For the display support it's ver

> Just look at how many projects are using Linux and cuda and don't support AMD. That's because of the CUDA api specifically. For the display support it's very hit/miss. Somethings work fine, then you want to try Wayland and things get odd... When working correctly they Nvidia is mostly fine - Xorg games have support for everything except dlss3 AFAIK.

charcircuit 3y ago
>That's because of the CUDA api specifically. No, if they wanted to support AMD they would provide an alternative GPU implementation that worked on their. It's like saying an app only supports Windows because of the Windows API. If someone wanted to support multiple apps they wouldn't just use the Windows API.
- thewataccount 3y ago
  > No, if they wanted to support AMD they would provide an alternative GPU implementation that worked on their. AMD's implementation (ROCm) has historically been incredibly difficult to work with. As in their own examples won't compile. Historically if you even wanted to _touch_ data-science you had to have CUDA hardware/software (it's been improving a bit but alternatives are still lacking). > It's like saying an app only supports Windows because of the Windows API. It's a little more nuanced than that because the CUDA api is specifically for one set of tasks - data science. Nobody uses nvidia for their wide desktop support on linux - because it's terrible. Literally the only benefit of using nvidia + linux is either because of raw performance of the hardware and/or the cuda support. If you look at the arch wiki (applies to other OSes too) for anything graphics related you'll almost always seen specific sections dedicated to workarounds and fixes for nvidia hardware. If you don't believe me then try setting up wayland with nvidia drivers. Steam just had a fun issue where they were crashing on nvidia hardware with their latest redesign (no idea how they didn't catch that?!). These types of issues are commonplace, and are largely avoided by using AMD. thus why I say it's only really because of the cuda support.

charcircuit 3y ago

>That's because of the CUDA api specifically. No, if they wanted to support AMD they would provide an alternative GPU implementation that worked on their. It's like saying an app only supports Windows because of the Windows API. If someone wanted to support multiple apps they wouldn't just use the Windows API.

thewataccount 3y ago
> No, if they wanted to support AMD they would provide an alternative GPU implementation that worked on their. AMD's implementation (ROCm) has historically been incredibly difficult to work with. As in their own examples won't compile. Historically if you even wanted to _touch_ data-science you had to have CUDA hardware/software (it's been improving a bit but alternatives are still lacking). > It's like saying an app only supports Windows because of the Windows API. It's a little more nuanced than that because the CUDA api is specifically for one set of tasks - data science. Nobody uses nvidia for their wide desktop support on linux - because it's terrible. Literally the only benefit of using nvidia + linux is either because of raw performance of the hardware and/or the cuda support. If you look at the arch wiki (applies to other OSes too) for anything graphics related you'll almost always seen specific sections dedicated to workarounds and fixes for nvidia hardware. If you don't believe me then try setting up wayland with nvidia drivers. Steam just had a fun issue where they were crashing on nvidia hardware with their latest redesign (no idea how they didn't catch that?!). These types of issues are commonplace, and are largely avoided by using AMD. thus why I say it's only really because of the cuda support.