Interesting how they made plugins for AMD and Nvidia. It's a smart strategy:
Intel knows they have no chance of competing against CUDA if they make OneAPI proprietary or exclusive. Sure, they could support some other open standard, but if they can make their own that performs better than OpenCL, that would give them an edge. By giving AMD and Nvidia compatibility whether they asked for it or not, this allows more developers to consider adopting it. In another perspective, many devs avoid CUDA because it is vendor locked, or conversely, many people avoid software because it depends on CUDA. Meanwhile, so long as Intel optimizes their side of things, they will come out looking the best, which matters when there are alternatives to compare to. I'm sure AMD and Nvidia could make their own drivers/plugins if they really wanted to, but Nvidia has to much pride and AMD doesn't like spending that kind of R&D money, leaving Intel to look like the better deal overall.
Intel knows they have no chance of competing against CUDA if they make OneAPI proprietary or exclusive. Sure, they could support some other open standard, but if they can make their own that performs better than OpenCL, that would give them an edge. By giving AMD and Nvidia compatibility whether they asked for it or not, this allows more developers to consider adopting it. In another perspective, many devs avoid CUDA because it is vendor locked, or conversely, many people avoid software because it depends on CUDA. Meanwhile, so long as Intel optimizes their side of things, they will come out looking the best, which matters when there are alternatives to compare to. I'm sure AMD and Nvidia could make their own drivers/plugins if they really wanted to, but Nvidia has to much pride and AMD doesn't like spending that kind of R&D money, leaving Intel to look like the better deal overall.
Comment