• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle






  • Two@lemmy.worldtoLinux@lemmy.mlNVK Has landed!
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    That is because it’s an open standard, not open source. You can read the documentation and implement a driver for a new platform, but you’re not porting vulkan to it. Likewise, there is tons of windows only open source code that will never work anywhere else because they target windows specific code.


  • Two@lemmy.worldtoLinux@lemmy.mlNVK Has landed!
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    No, its not. With open source software you, a regular person, can feasibly get a change included into the code base. That is NOT true with an open standard. You, or more accurately a very large and powerful company you work with or for, have to have significant pull to even hope to get a change in. Even then, those changes take a lot of time to proliferate.

    With open source code that change can happen as soon as you write it, you don’t even have to wait for the maintainer to merge it; just fork the software. You can’t really “fork” Vulkan as a normal dev; no one will follow your spec. You don’t have enough pull as a single dev to get billion dollar companies to follow it. But you can relatively easily get those same companies to use your fork of an open source software.

    They are entirely different systems.


  • Two@lemmy.worldtoLinux@lemmy.mlNVK Has landed!
    link
    fedilink
    arrow-up
    9
    ·
    1 year ago

    If you’re on Linux Vulkan is the way to go. Unless their use of the standard is really bad, Vulkan will always perform better on Linux than DirectX 12

    If you’re on Windows, then it can be a bit of a crap shoot on which one performs better.