Vulkan, Forging Ahead - SIGGRAPH 2023 BOF Session

Seven years after its introduction, Vulkan continues to evolve to serve the needs of high-performance graphics applications. Catch the latest news from the Vulkan Working Group and members of the Vulkan community.

0:00:00 - Vulkan Update
0:35:39 - Vulkan SDK and Ecosystem Tools
0:58:02 - Teaching Vulkan
1:32:04 - Vulkan and Open Source Graphics at Autodesk
1:38:53 - Vulkan Ray Tracing in Aurora: An Open Source Real-Time Path Tracer
2:03:13 - Porting Autodesk Flame from OpenGL to Vulkan
2:13:41 - Basic Ray Trace Debugging in Vulkan

Presenters: Tom Olson (Vulkan WG Chair/ Arm), Karen Ghavam (Lunar G), Lukas Lipp (TU Wien) & Bernhard Kerbl (INRIA), Henrik Edstrom (Autodesk), Mauricio Vives (Autodesk), Vipul Kapoor (Autodesk), Jasmin Roy (Autodesk), Hai Nguyen (Independent)

[syntaxed]

Vulkan is credited as the future graphics interface - but the API is full of various const char**, static casts and other obsolete C shittery.
The entire thing is an oxymoron if you ask me, how can you design something for the future and still support C?