3 ms·

> And it's probably motivated by a desire to generate lock-in for their hardware. I don't see how MIT licensed code can generate lock-in for AMD hardware. Woul

by SXX 11y ago

> And it's probably motivated by a desire to generate lock-in for their hardware. I don't see how MIT licensed code can generate lock-in for AMD hardware. Would you care to elaborate?

sevensor 11y ago
Perhaps I'm misreading it, but the announcement seemed to imply that the source code, however open, is for AMD hardware. So by open-sourcing it, they attempt to generate lock-in to the hardware, which is still just as proprietary as can be. In other words, I don't think that these tools will work on your NVidia GPU. Or not well, at any rate.
- SXX 11y ago
  Yeah you misreading it because on slides there is few different things and some of them was already announced in past: * Open source game and rendering middleware, tools and most of it is for Direct3D11/12, but some things is OpenCL / OpenGL. None of it can be AMD-only because it's all based around standard APIs. Techs that Nvidia provide with GameWorks only support hardware acceleration on top of CUDA which is proprietary. * HSA-related stuff include compiler from CUDA. I'm not expert in this area, but HSA is also not just AMD-only thing and there is several companies backing it. * Linux graphics stack. It's of course AMD-only, but AMD announced that they'll open source their OpenCL and Vulkan implementation so other vendors may benefit of it. So no. They don't release things that can only be used with AMD GPUs or anything like that. What more important anyone can take MIT licensed code and turn it into the proprietary product, etc.
  - andromeduck 11y ago
    but most of the stuff people complain about in gameworks is multiplatform in the same way - especially hairworks
    - SXX 11y ago
      Main issue with that part of Nvidia middleware is proprietary license so no one can publicly share improvements for other vendors GPUs. Also as far as I understand the default licensing option for most of Nvidia middleware don't contain source code at all.
  - sevensor 11y ago
    Thanks for the correction!

by SXX 11y ago

> And it's probably motivated by a desire to generate lock-in for their hardware. I don't see how MIT licensed code can generate lock-in for AMD hardware. Would you care to elaborate?

sevensor 11y ago

Perhaps I'm misreading it, but the announcement seemed to imply that the source code, however open, is for AMD hardware. So by open-sourcing it, they attempt to generate lock-in to the hardware, which is still just as proprietary as can be. In other words, I don't think that these tools will work on your NVidia GPU. Or not well, at any rate.

SXX 11y ago
Yeah you misreading it because on slides there is few different things and some of them was already announced in past: * Open source game and rendering middleware, tools and most of it is for Direct3D11/12, but some things is OpenCL / OpenGL. None of it can be AMD-only because it's all based around standard APIs. Techs that Nvidia provide with GameWorks only support hardware acceleration on top of CUDA which is proprietary. * HSA-related stuff include compiler from CUDA. I'm not expert in this area, but HSA is also not just AMD-only thing and there is several companies backing it. * Linux graphics stack. It's of course AMD-only, but AMD announced that they'll open source their OpenCL and Vulkan implementation so other vendors may benefit of it. So no. They don't release things that can only be used with AMD GPUs or anything like that. What more important anyone can take MIT licensed code and turn it into the proprietary product, etc.
- andromeduck 11y ago
  but most of the stuff people complain about in gameworks is multiplatform in the same way - especially hairworks
  - SXX 11y ago
    Main issue with that part of Nvidia middleware is proprietary license so no one can publicly share improvements for other vendors GPUs. Also as far as I understand the default licensing option for most of Nvidia middleware don't contain source code at all.
- sevensor 11y ago
  Thanks for the correction!