Also just joking :-)
Almost 4000 pages of specification. Just device creation can take a week or so only to fill out structures for device properties and chain them together in a huge amorphous mass. That's many hundreds of lines of not very intelligent code, scrolled out and beyond view, but still causing errors and ambiguities or even contradictions.
SPIRV is, compared to GLSL or HLSL underdefined and not human readable. And I must rely on 3rd party products from Google or LunarG. Can I be sure that some SPIRV compiler knows the right spell for the GLSL shader I did, or even does what it is meant for ?
All this because someone finds that one API should be stuffed with every case for every hardware and application, an approach that up to now has never worked in any kind of engineering. Already ludicrously long and screen filling naming conventions that obfuscate the meaning of the code are being numbered because a new case has emerged. I name that unprofessional.
This is running out of control for indie devs. Thanks, but no thanks. At a certain age, lifetime becomes more important than filling out papers. There's my frustration with Vulkan. Idk, am I the only one ?
