# Vulkan 99 Hacker News commenters recommended Vulkan and 60 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months. **Verdict:** An open, cross-platform GPU API for graphics and compute, often faster than ROCm for local AI, but verbose, boilerplate-heavy and hard to learn. ## Why people recommend it - Open, cross-platform standard (10 comments): "There's a complete graphics ecosystem with full participation from the games industry that doesn't have Microsoft as the gatekeeper." ([source](https://news.ycombinator.com/item?id=45922273)) "Vulkan makes no such assumptions, and uses no platform-specific data structures, making it automatically more cross-platform." ([source](https://news.ycombinator.com/item?id=46024639)) "My definition of open is that Khronos doesn't restrict (as far as I know) what platforms Vulkan can be implemented on." ([source](https://news.ycombinator.com/item?id=46024876)) - Fast GPU compute, beats ROCm (5 comments): "Vulkan is up to 2.25X faster for most coalesced, strided and interleave variants for memory-side scheduling/access shapes" ([source](https://news.ycombinator.com/item?id=48827260)) "one is incredibly more stable (and sometimes even more performant) for AI use cases as side-gig" ([source](https://news.ycombinator.com/item?id=47750455)) "ROCm is usually not only a bit slower for me (~32 t/s vs ~43 t/s on the main model I use)" ([source](https://news.ycombinator.com/item?id=47824179)) - Modern extensions simplify code (4 comments): "Vulkan is miserable, but several things are improved by using a few extensions supported by almost all relevant vendors." ([source](https://news.ycombinator.com/item?id=46011121)) "Using Vulkan 1.3 with a few extensions is actually far more ergonomic beyond a basic "Hello, World" than using SDL GPU." ([source](https://news.ycombinator.com/item?id=46012156)) "Going from render passes to dynamic rendering really simplified my code." ([source](https://news.ycombinator.com/item?id=46959825)) - Broad industry and engine support (4 comments): "There's a complete graphics ecosystem with full participation from the games industry that doesn't have Microsoft as the gatekeeper." ([source](https://news.ycombinator.com/item?id=45922273)) "Vulkan is mature. It has been used in production since 2013 (!) in the form of Mantle." ([source](https://news.ycombinator.com/item?id=46966015)) "Vulkan has the shape of every modern graphics api out there, DX included." ([source](https://news.ycombinator.com/item?id=49023983)) ## What people warn about - Heavy boilerplate, steep learning curve (5 comments): "you'll probably burn yourself out by the time you've gotten a triangle on the screen" ([source](https://news.ycombinator.com/item?id=49028867)) "it's very convoluted low-level API, in which you have to write pretty complicated 200+LoC just to have simplest stuff running" ([source](https://news.ycombinator.com/item?id=47749271)) "These low level concepts are just unnecessary “learning cliffs” that are only useful to existing experts in the field." ([source](https://news.ycombinator.com/item?id=46011660)) - Needlessly complex API design (3 comments): "There are so many completely needlessly complex things, or things that should have an easy-path for the common case." ([source](https://news.ycombinator.com/item?id=46961965)) "Vulkan still requires you to play by someone else's rules of how they thought the API should work" ([source](https://news.ycombinator.com/item?id=48919145)) "I'm not going to use an API with entirely pointless complexity with zero performance benefits for my use cases." ([source](https://news.ycombinator.com/item?id=46965933)) - Committee and mobile-driven design compromises (5 comments): "a collection of more-or-less adhoc design decisions to make Vulkan 1.0 work on specific GPUs" ([source](https://news.ycombinator.com/item?id=49461264)) "Render passes were only bolted into Vulkan because of mobile tiler GPUs, they never made any sense for desktop GPUs and only made Vulkan worse for desktop graphics development." ([source](https://news.ycombinator.com/item?id=46323427)) "The mistake Vulkan made was putting too much state in the pipeline, as much of that state is dynamic in modern hardware now." ([source](https://news.ycombinator.com/item?id=46353147)) ## Alternatives hackers recommend - [OpenGL](https://hackerapproved.com/p/opengl.md): 39 recommend - [WebGPU](https://hackerapproved.com/p/webgpu.md): 35 recommend - [Metal](https://hackerapproved.com/p/metal.md): 27 recommend - [DirectX](https://hackerapproved.com/p/directx.md): 25 recommend - [SDL_GPU](https://hackerapproved.com/p/sdl-gpu.md): 7 recommend ## Cite as Hacker Approved, "Vulkan", https://hackerapproved.com/p/vulkan/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).