An attempt at Vulkan

OpenGL delegates the “name-to-address” translation to the graphics driver (acting as a black box), whereas Vulkan places this burden on you, the engine developer. OpenGL’s Approach: Driver as a “Nanny” Service In OpenGL, the graphics driver is a complex, monolithic system. When you compile a shader, the driver internally and automatically builds a lookup table or “dictionary”. My Current Dilemma: Should I emulate OpenGL’s approach by implementing my own dictionary system, or is there a more modern, efficient mapping strategy I should adopt instead? In fact, no matter which method is used, modifying the shader is inevitable. But fortunately, the material system of JME can still be used.