VulkanSceneGraph VS misc

I have not used this, but heard good things about Vulkan Scene Graph. https://github.com/vsg-dev/VulkanSceneGraph Like Open Scene Graph, it's more than just a scene graph. It provides math and geometry among other abstractions for computer graphics.

Pipelines (or in general terms PSOs) are the most problematic aspect of Vulkan / DX12 - much more than synchronization! Large parts of the gamedev industry seems to recognize all the performance issues with pipelines and therefore companies are experimenting with newer models like the VK_EXT_shader_object extension ("Vulkan without Pipelines": https://www.khronos.org/blog/you-can-use-vulkan-without-pipe...).

I've written a detailed comment about this before here (https://news.ycombinator.com/item?id=37843946#37845431) but for a much more comprehensive explanation by an engineer from Nintendo read the initial proposal for the VK_EXT_shader_object extension: https://github.com/KhronosGroup/Vulkan-Docs/blob/main/propos...).

There's also Casey Muratori's mail to the Vulkan advisory on 2015 that basically predicts this whole clusterfuck would happen: https://github.com/cmuratori/misc/blob/main/vulkan_dynamic_s...

Casey and Uncle Bob did have a conversation about the architectural part of Clean Code - unfortunately it seems to have ended just as it was getting interesting. I did want to add some of my thoughts to your comment though.

I'll put the link to Casey and Uncle Bob's discussion about architecture here again. This discussion is specifically about maintainability. In it they both come up with a design for a device IO API, and argue its strengths in terms maintainability and extensibility.