Stop Using the Vulkan API

STOP USING Vulkan API • API'S WERE NOT MEANT TO BE OVERCOMPLICATED • YEARS OF FULL CONTROL OVER GRAPHICS PIPELINE YET NO REAL USE FOUND FOR pipelineTessellationStateCreateInfo.patchControlPoints • WANTED TO CONTROL FULL GRAPHICS PIPELINE FOR A LAUGH? We had a tool for that, it was called CPU RENDERING • “Yes, give me VkPipelineDepthStencilStateCreateInfo” – Statements dreamt up by the utterly deranged LOOK at what Vulkan developers have been demanding your Respect for all this time, with all structures we built for them VkPipelineVertexInputStateCreateInfo pipelineVertexInputStateCreateInfo(); pipelineVertexInputStateCreateInfo.sType = VK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_STATE_CREATE_INFO; pipelineVertexInputStateCreateInfo.vertexBindingDescriptionCount = static_cast<uint32_t>(vertexBindingDescriptions.size()); pipelineVertexInputStateCreateInfo.pVertexBindingDescriptions = vertexBindingDescriptions.data(); pipelineVertexInputStateCreateInfo.vertexAttributeDescriptionCount = static_cast<uint32_t>(vertexAttributeDescriptions.size()); pipelineVertexInputStateCreateInfo.pVertexAttributeDescriptions = vertexAttributeDescriptions.data(); ????? ??????????? ?????????????? “Hello I would like configInfo.colorBlendAttachment.dstAlphaBlendFactor please” They have played us for absolute fools

Текстовый мем высмеивает чрезмерно сложный API Vulkan и огромное количество структур и полей, необходимых даже для простых задач. Шутка в том, что разработчики якобы требуют полного контроля над графическим конвейером, но результат выглядит как бессмысленная пытка с длинными именами и загадочными параметрами. Мем используют программисты как реакцию на чрезмерную сложность, бюрократию и плохой дизайн API.

• @profunctor_io / 6821 2021-07-04