3 ms·

Khronos is a standards group. It's their job to make standards, not tooling. Individual vendors that are part of Khronos can make tooling.

pjmlp 8y ago
Then they made a bad standard to start with. Also regarding tooling, that isn't quite true, as they have engaged with LunarG for Vulkan, because they have learned from lack of OpenGL adoption, that the large majority of games developers wouldn't even bother without a proper SDK.
- geezerjay 8y ago
  > Then they made a bad standard to start with. Nonsense. You'll be hard-pressed to find a platform that doesn't support C or a competent system design or even graphics design engineer who isn't confortable with C. If their goal is to establish standards, they build upon standards.
  - pjmlp 8y ago
    Developers jumping on CUDA due to lack of C++ and Fortran support on OpenCL proves how good that decision was. Likewise for game consoles, Windows and now Apple graphics APIs. Defining standards does not mean they must provide a lowest denominator single implementation. They can be defined in an IDL kind of way, like e.g. WebIDL, abstractly e.g. Internet RFCs, or define mappings to all major languages in the GPGPU field, namely C, C++ and Fortran.
    - pcwalton 8y ago
      > They can be defined in an IDL kind of way, like e.g. WebIDL, abstractly e.g. Internet RFCs, or define mappings to all major languages in the GPGPU field, namely C, C++ and Fortran. That's already done. Mozilla's Obsidian is an object-oriented WebIDL interface to Vulkan: https://github.com/KhronosGroup/WebGLNext-Proposals/tree/master/Obsidian-Mozilla https://github.com/KhronosGroup/WebGLNext-Proposals/tree/mas... Again, Khronos is just a standards group. It does what its members tell it to. Khronos is far more lightweight of an organization than, say, ISO's C++ committee. Instead of blaming Khronos, you could perhaps encourage them to focus on initiatives like Obsidian.
deleted 8y ago
[deleted]

pjmlp 8y ago

Then they made a bad standard to start with. Also regarding tooling, that isn't quite true, as they have engaged with LunarG for Vulkan, because they have learned from lack of OpenGL adoption, that the large majority of games developers wouldn't even bother without a proper SDK.

geezerjay 8y ago
> Then they made a bad standard to start with. Nonsense. You'll be hard-pressed to find a platform that doesn't support C or a competent system design or even graphics design engineer who isn't confortable with C. If their goal is to establish standards, they build upon standards.
- pjmlp 8y ago
  Developers jumping on CUDA due to lack of C++ and Fortran support on OpenCL proves how good that decision was. Likewise for game consoles, Windows and now Apple graphics APIs. Defining standards does not mean they must provide a lowest denominator single implementation. They can be defined in an IDL kind of way, like e.g. WebIDL, abstractly e.g. Internet RFCs, or define mappings to all major languages in the GPGPU field, namely C, C++ and Fortran.
  - pcwalton 8y ago
    > They can be defined in an IDL kind of way, like e.g. WebIDL, abstractly e.g. Internet RFCs, or define mappings to all major languages in the GPGPU field, namely C, C++ and Fortran. That's already done. Mozilla's Obsidian is an object-oriented WebIDL interface to Vulkan: https://github.com/KhronosGroup/WebGLNext-Proposals/tree/master/Obsidian-Mozilla https://github.com/KhronosGroup/WebGLNext-Proposals/tree/mas... Again, Khronos is just a standards group. It does what its members tell it to. Khronos is far more lightweight of an organization than, say, ISO's C++ committee. Instead of blaming Khronos, you could perhaps encourage them to focus on initiatives like Obsidian.

deleted 8y ago

[deleted]