Announcement

Collapse
No announcement yet.

Vulkan 1.0.50 Adds New AMD-Developed Extension

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vulkan 1.0.50 Adds New AMD-Developed Extension

    Phoronix: Vulkan 1.0.50 Adds New AMD-Developed Extension

    Vulkan 1.0.50 is now available as the latest point release to the specification for this high-performance, cross-platform graphics API...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    ...Why is the Vulkan "standard" getting extensions specifically named for specific companies? :/

    If this is only useful for AMD, it shouldn't be in the standard (or, rather, "any standard at all"), and if it's useful for others, it shouldn't have AMD in the name.

    Probably not the first extension that they've done this with, but still, seems odd to me. Standards should be... standard. Not vendor-specific. That's what Mantle is/was for.

    Standards should guarantee compatibility and should never, ever allow any vendor-specific stuff. Ever.
    Last edited by Holograph; 22 May 2017, 03:58 PM.

    Comment


    • #3
      Originally posted by Holograph View Post
      ...Why is the Vulkan "standard" getting extensions specifically named for specific companies? :/

      If this is only useful for AMD, it shouldn't be in the standard (or, rather, "any standard at all"), and if it's useful for others, it shouldn't have AMD in the name.

      Probably not the first extension that they've done this with, but still, seems odd to me. Standards should be... standard. Not vendor-specific. That's what Mantle is/was for.

      Standards should guarantee compatibility and should never, ever allow any vendor-specific stuff. Ever.
      None of the vendors were willing to use Vulkan unless they could keep adding their own extensions to it, just like they could under OpenGL. That was a decision they all made when they created Vulkan, and it's not changing.

      They're all optional, of course. And unlike GL, applications have to explicitly ask for them rather than just getting everything applied automatically.

      The idea behind the naming is still the same - vendor specific extensions are labelled that way (though of course other vendors can implement them as well) and if the extension is successful and others want to jump in it gets renamed to KHR.

      Comment

      Working...
      X