I learned Vulkan and wrote a small game engine with it (edw.is)

Article summary

The author learned Vulkan and wrote a small game engine with it in 3 months, despite having no prior knowledge of Vulkan. The author had previous experience with OpenGL and game engine development, which helped with the transition. The engine is designed for small, level-based games and is open-source. The author shares their experience and provides advice for those interested in learning Vulkan.

Main themes

• Vulkan learning
• Game engine development
• Graphics programming
• Software engineering
• API choice

What commenters say

• Learning Vulkan can be challenging, but with the right resources and approach, it can be manageable, even for those without prior experience.
• Some argue that Vulkan is not necessary for small games and that other APIs like OpenGL or WebGPU may be sufficient.
• Over-engineering solutions can lead to unnecessary complexity and maintenance issues, and it's essential to focus on solving the current problem rather than anticipating future needs.
• Others counter that under-engineering solutions can also lead to problems, and that investing time and care in building solid foundations can pay off in the long run.
• The choice of API depends on the specific use case, and factors like performance, hardware features, and development ease should be considered.
• Some developers believe that writing simple, maintainable code is possible without sacrificing functionality or performance, while others see a trade-off between simplicity and extensibility.