Perhaps, but Apple certainly doesn't mind releasing something as small as a Security Update which wreaks havoc with nVidia drivers. So, as an nVidia and Apple user, I delay the benefit of the Apple security update until it's supported by an nVidia driver update. How does that benefit the Apple universe? It doesn't yet it still happens.
NVidia breaks themselves automatically if the build number changes. That was totally Nvidia's fault, not Apple's. It's a "feature" Nvidia added.
Apple shouldn't be expected to tiptoe around other developer's "features" like that. It would be crazy to think Apple should not be able to update their own build numbers or version numbers without Nvidia's permission.
As far as killing CUDA, Apple never supported it to begin with. They're not going to have an NVidia option just for CUDA when it's not an officially supported technology and it never has been. It's like saying you won't buy a Mac Pro
because it doesn't come with a Soundblaster because you have some app that is Soundblaster accelerated. That's ok, but you can't expect Apple to throw in every bell and whistle for any random technology in the world that isn't officially supported.
[doublepost=1454318332][/doublepost]
Furthermore, Apple has alienated these developers by staying on OpenCL 1.2. The rest of the world has already OpenCL 2.0 available. So if you really want up-to-date cross platform technology, CUDA is the only proven option on OS X right now. (And with Metal the cross platform gap even widens.)
"Up to date" is relative. CUDA hasn't changed much in a long time.
Nvidia also only supports OpenCL 1.2 on Windows, so if you're an OpenCL developer, the lack of OpenCL 2.0 is disappointing, but if you can't use it universally on Windows either, not that big of a deal.
If Nvidia doesn't have a 2.0 driver at all, it could be a reason Apple hasn't implemented it yet, and maybe another reason they are busy ridding themselves of Nvidia based Macs. NVidia really doesn't seem to care about compute.