Khronos Vulkan 1.0

It's out. Discuss!

https://www.khronos.org/registry/vulkan/

Spec:
https://www.khronos.org/registry/vulkan/specs/1.0/xhtml/vkspec.html
https://www.khronos.org/registry/vulkan/specs/1.0/pdf/vkspec.pdf

>>40
No, it shouldn't.

>>40
I don't think it should be regulated. If you know about the ISO 9000 standard, you would know that there are already standards regarding the operation of a business and the quality of the product/service that's delivered.

The only licensed programmers are the knights of lambda calculus!

Render my dubs

>>40
No, no, no, no, NO! The last thing we need is more corporate bureaucracy with no doubt the user-hostile "security" and DRM-loving faggots getting involved too.

>>42
The correct standard is ISO 9001:2008. IT'S OVER 9000!!!!!!!!11

>>45
You're no professional, Cudder.

>>46
And proud of it.

"Amateurs built the ark. Professionals built the Titanic."

>>45-47
I miss the old Cudder.

Anyone who really wants a programming license needs to be put to the rope, seriously. What the fuck is wrong with you, fool?

A programming license would be like a hammering license.
Instead, make it so you need a license depending on what you want to hammer.
So, y can hammer a nail into a plank of wood you own without a license, but if you try to hammer a brain tumour, you'll need to get a license. If you try to hammer a space rocket containing live humans, you'll need a license. If you try to do some high-frequency stock market hammering, you'll need a license.
Et cetera.

>>50
Applied in the shit way the industry and bureaucracy always work, it'll take the more literal approach of needing a license for Java, a license for Python, a license for AWS, a license for Visual Studio, etc. In other words, completely missing the point of what programming and software engineering actually is.

>>40
this kind of nu-security approach really pisses me off. oldschool hacker approach to security was about education and experimentation, nu-security wants everything to be like a fucking mobile phone. the DON'T TOUCH ANYTHING AND LET BIG GUYS DO THEIR WORK shit is going to doom industry

>>51
basically, it would be legislated certificate fetishism, but with bonus government inefficiency. expect exams on which you'll need to calculate large prime numbers by hand and memorize opcodes

Should fetishism be a regulated activity?

>>54
Check 'em

Anyone know when I can get Vulkan to work on my Radeon HD7950 GPU on Linux? I know it's not supported at least at the beginning by Catalysty. What about Mesa?

>>56

Radeon HD7950 GPU

Your GPU won't ever be supported by AMD, at least not in the short to medium term. Vulkan will only be available with the new AMDGPU kernel driver, and that means Sea Islands/Volcanic Islands chipsets and later. Your only hope there is for Vulkan to eventually show up in Mesa and get backported for use with Radeon/Radeonsi drivers.

Thing is, AMD hasn't even released proprietary Linux drivers with Vulkan support yet. I was thinking about heading down and grabbing an nVidia GPU for my home system, but decided against it at the last minute. AMD better get their shit together.

Also, the 4.5 Linux kernel sure is taking a fucking long time to get out of RC purgatory. What gives?