"If you're not using #VMA [for application space programming], you're not using #Vulkan correctly"
- Chris Glover's #Vulkanised Keynote
@rml Ignore vulkan-tutorial unless you're familiar with opengl. Take vkguide.dev instead.
@dpwiz I actually worked professionally with opengl for years, so I'll check out both :) thanks
@rml IMO, v-t is a bit too conservative. It helps to set up a basic flow of it but doesn't really teach you much of what makes vulkan interesting. vk-guide does a better job of it.
Anyway, it's trawling the specs and forums afterwards while enjoying the new intimate connection to hardware 
@dpwiz yeah, I think thats the key, don't go into vulkan expecting to improve your graphics programming, go to learn how to grok gpus and eventually be able to get cheap graphics on Linux
@dpwiz I'm about to embark on Vulkan for the first time, understanding that I won't be using it to get pixels on the screen soon, but rather just to get down to the nitty gritty of GPUs in hopes to start contributing to Linux graphics. any tips, blog posts, etc that helped you along the way?