3 ms·
Because Nvidia likes lock-in. It totally doesn't have to. Today we have Vulkan for general purpose GPU programming.
by shmerl 7y ago
Because Nvidia likes lock-in. It totally doesn't have to. Today we have Vulkan for general purpose GPU programming.
- llukas 7y agoOpenCL, hip, Vulkan, what tomorrow? Or alternatively, there were cl* libraries, roc* libraries and hip* libraries for AMD? Which ones are supported? CUDA doesn't require rewriting code with ${OSS} framework of the year, every year. They need to earn that lock-in with future compatibility guarantees which none of OSS projects has.
- shmerl 7y agoWhatever it is, as long as it's not tied to one GPU only, it could be promising. Something that's tied to Nvidia or anyone else exclusively is not good, and surely isn't democratizing anything. > CUDA doesn't require rewriting code with ${OSS} framework of the year, every year. How so? Change the GPU from Nvidia, and you are forced to rewrite code. That's the whole point of lock-in, it's a tax on developers. CUDA doens't guarantee you anything, if you don't stick with their GPUs. Vulkan on the the other hand has conformance requirements.