Announcement

Collapse
No announcement yet.

Vulkan 1.0.11 Is The Latest, Scripts/XML/Headers Changed To Apache License

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

  • Vulkan 1.0.11 Is The Latest, Scripts/XML/Headers Changed To Apache License

    Phoronix: Vulkan 1.0.11 Is The Latest, Scripts/XML/Headers Changed To Apache License

    There's another weekly point release of the Vulkan high performance 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
    I suspect re-licensing was asked by downstream so they don't have to involve lawyers to review another open source license. So Khronos opted for most closest one - so it is a win/win situation.

    Comment


    • #3
      No offense, but if they have to patch their s*it every week, it's probably not very well thought. I remember the days when version numbers meant something and programmers were programmers.

      Comment


      • #4
        Originally posted by wargames View Post
        No offense, but if they have to patch their s*it every week, it's probably not very well thought. I remember the days when version numbers meant something and programmers were programmers.
        So programmers in most active open source projects aren't programmers, just because there are commits, changes and new version releases all the time?

        Comment


        • #5
          Originally posted by PyroDevil View Post

          So programmers in most active open source projects aren't programmers, just because there are commits, changes and new version releases all the time?
          Correct, programmers do everything correctly the first time and never have to update. The more updates you do the further you are from a real programmer.

          Comment


          • #6
            Originally posted by Vash63 View Post

            Correct, programmers do everything correctly the first time and never have to update. The more updates you do the further you are from a real programmer.
            Then I suppose that the programmers on Dolphin, Citra, Google Chrome, Linux, and pretty much any active popular application are not really a real programmer.

            Comment


            • #7
              Nintendo's upcoming NX console should be a boost to the Vulkan exosystem

              using a Polaris-based GPU, and goes with the announcement of Nintendo joining Kronos. But the dev I spoke to about the GPU, who is porting a PS4 game to NX said Vulkan is not ready yet (as of the 2015 December SDK, should be an update in May) and they are using a variation of the PS4 API, GMNX, until Vulkan is ready.

              Comment


              • #8
                Originally posted by wargames View Post
                No offense, but if they have to patch their s*it every week, it's probably not very well thought. I remember the days when version numbers meant something and programmers were programmers.
                Vulkan is API stable (next API update will be 2.0), so these releases are for driver writers only - except well for docs, but those can be accessed by developers all the time. For drivers this means clarifying how everything works mostly. API is still valid and apps will run on drivers based on older patch version, just having newer driver using 1.0.11 will be more optimized.

                Comment


                • #9
                  Originally posted by humbug View Post
                  Nintendo's upcoming NX console should be a boost to the Vulkan exosystem


                  http://wccftech.com/nintendo-nx-alle...evelopment-ip/
                  That story is debunked however. Not sure if Vulkan part is wrong too. However Nintendo is with Khronos so it wouldn't make much sense for them to be there otherwise.

                  Comment


                  • #10
                    Originally posted by Vash63 View Post
                    Correct, programmers do everything correctly the first time and never have to update. The more updates you do the further you are from a real programmer.
                    This was possible (theoretically) in the distant past maybe, when real men wrote in cobol and punched cards, the intercommunication between machines was crude and not anywhere near performant or safe, and computers weren't even multiprogramming so programs could not even talk to each other.

                    Unless your work consists in writing "hello world" projects, you will have to update stuff every now and then as everything you base your work on and everything that uses your work changes.

                    Comment

                    Working...
                    X