No Graphics API (sebastianaaltonen.com)

Article summary

The article discusses the complexity of modern graphics APIs, such as DirectX 12 and Vulkan, and how they have become outdated due to advancements in GPU architecture. The author argues that these APIs were designed for older hardware and are no longer necessary, leading to unnecessary complexity and performance issues. A new, simplified API could take advantage of modern GPU capabilities and improve performance. The article also explores the history of graphics APIs and their evolution over time.

Main themes

• Graphics API complexity
• GPU architecture evolution
• Performance optimization
• API design
• Hardware advancements
• Rendering pipelines

What commenters say

• The current graphics APIs are outdated and in need of simplification to take advantage of modern GPU capabilities.
• Unifying desktop and mobile GPU APIs is not practical due to significant differences in hardware and performance requirements.
• Mobile GPUs are holding back desktop graphics development due to the need to support outdated hardware and drivers.
• A separate API for mobile and desktop GPUs would be more effective than a unified API.
• The lack of innovation in graphics APIs is due to vendor lock-in and a lack of interest in reinventing the wheel.
• The complexity of current graphics APIs is a significant barrier to adoption and use, particularly for developers who are not experts in graphics programming.
• The use of precompiled pipeline states in modern APIs can lead to performance issues and is not necessary with modern GPU hardware.
• A simpler API could enable better performance and more efficient use of GPU resources, but it would require significant changes to existing rendering pipelines and developer workflows.