←back to thread

1045 points mfiguiere | 1 comments | | HN request time: 0.298s | source
Show context
wheybags ◴[] No.39345186[source]
Cannot understand why AMD would stop funding this. It seems like this should have a whole team allocated to it.
replies(1): >>39345254 #
otoburb ◴[] No.39345254[source]
They would always be at the mercy of NVIDIA's API. Without knowing the inner workings, perhaps a major concern with this approach is the need to implement on NVIDIA's schedule instead of AMD's which is a very reactive stance.

This approach actually would make sense if AMD felt, like most of us perhaps, that the NVIDIA ecosystem is too entrenched, but perhaps they made the decision recently to discontinue funding because they (now?) feel otherwise.

replies(2): >>39345418 #>>39347490 #
blagie ◴[] No.39345418[source]
They've been at mercy of Intel x86 APIs for a long time. Didn't kill them.

What happens here is that the original vendor loses control of the API once there are multiple implementations. That's the best possible outcome for AMD.

In either case, they have a limited window to be adopted, and that's more important. The abstraction layer here helps too. AMD code is !@#$%. If this were adopted, it makes it easier to fix things underneath. All that is a lot more important than a dream of disrupting CUDA.

replies(3): >>39345550 #>>39345891 #>>39346080 #
rubatuga ◴[] No.39345550[source]
x86 is not the same, the courts forced the release of x86 architecture to AMD during an antitrust lawsuit
replies(2): >>39345691 #>>39345787 #
1. hardware2win ◴[] No.39345787[source]
You think x86 would be changed in such a way that it'd break and?

Because what else?

If so, then i think that this is crazy because software is harder to change than hardware