(no title)
blelbach | 5 years ago
I'm not sure what you're saying here? You think another company or organization should write all the software for our hardware?
I don't think you understand the semiconductor industry.
Our business model relies on hardware and software engineers working closely together, as I've described in other replies.
We would not be able to produce a viable product that is solely raw hardware.
Also, what motivation does this other organization or company have to create software for our hardware?
> The world will be better if any developer (paid by nivida or not) is able to write code for any GPU (sold by nvidia or not).
This library is something that is designed to help you write Standard C++ code that runs on our GPU. Standard C++ runs everywhere.
> It is not nvidia role to say how or when software will be written.
Providing the SDKs and toolchains to program our platform is definitely part of our role in the ecosystem.
> Their hardware is good and that's more than OK.
Our hardware is useless without our software.
> AI/CUDA code written specifically for nvidia is useless/deprecated in the long term. A lot of brain waste.
I expect CUDA will be around for a while.
jameshilliard|5 years ago
> Also, what motivation does this other organization or company have to create software for our hardware?
Typically an organization like this would be a user of nvidia hardware, that's like asking what motivation Microsoft has for writing software/toolchains for Intel hardware. Maybe this attitude is why nvidia is notorious for having a terrible open source software experience for Linux graphics.
> Our hardware is useless without our software.
It's not(https://nouveau.freedesktop.org/wiki/) but nvidia is considered one of the worst hardware vendors when it comes to having proper open source driver/toolchain support. The situation used to be even worse but it's still not great now.
dahart|5 years ago
blelbach|5 years ago
It's not hostility, it's about agility. More so than other hardware vendors, we rely on really tight integration between hardware and software.
In some situations, we find a hardware bug that would require another manufacturer to do a "respin" (e.g. restart the manufacturing process with a new, fixed design). Because we have tight control over the software stack, we can workaround that bug. It's faster for us to do this when we have full control. Also, sometimes these bugs have security implications, etc.
That said, we've been moving in the direction of open source for a long time.
> It's not(https://nouveau.freedesktop.org/wiki/)
The other fellow was suggesting we should write no software at all. Nouveau's struggles is an excellent example of how difficult it is to write software for hardware without the engagement and interaction of the manufacturer of that hardware.
TL;DR you're talking about whether our software should open source versus closed source; the other fellow was suggesting we shouldn't have software at all.