u/Latter_Relationship5

I have some ++basic OpenGL and D3D11 experience and I want to learn Vulkan properly from scratch , not just making things compile without understanding them.

The problem: most tutorials I find are outdated like https://vulkan-tutorial.com or use wrappers that abstract things to make things easier and avoid boilerplate like https://vkguide.dev . The official Khronos tutorial looks solid and modern (Vulkan 1.4, dynamic rendering, timeline semaphores) but uses vulkan.hpp with RAII instead of raw vulkan.h:
docs.vulkan.org/tutorial/latest

My concern is that vulkan.hpp will negatively affect the learning the Vulkan concepts or it doesn't matter since it is a thin wrapper.

Am I searching for the wrong thing, or are there basically no jobs that combine C++ and WebGPU (Google Dawn)?

I’ve been diving into WebGPU recently and I got really interested in the idea of using it with C++. I started looking around at job postings expecting to find at least some niche roles mixing both… but almost everything I find is either:

• WebGPU + TypeScript/JavaScript
• some WASM

Almost never WebGPU + C++ together. now I’m wondering:

-Does this role actually exist professionally yet, or is it still rare and uncommon compared to TS/JS ?

Would genuinely love insight from people closer to the industry because right now I feel like I’m searching for a ghost stack

I want to learn Unreal Engine 5 for non-gaming stuff (for now archviz).
im comfortable with C++ and have some basic graphics programming knowledge(Opengl/D3D11), so I’m not a complete beginner to graphics domain.
Most tutorials I find are very game-focused or too basic it doesn't involved C++ deeply, which isn’t super helpful. im wondering

• What’s the fastest way to get productive with UE5 in this context?
• What should I focus on first (C++, Blueprints, plugins)?
• Any solid resources that aren’t game-heavy?
• If blueprint is required , can i learn both C++/Blueprint simultaneously ?

If you’ve used UE5 outside of games, what actually helped you get up to speed?

Like with OpenGL, the code style changed a lot over time. Old fixed-function stuff looks very different from the newer shader-based way of doing things. Vulkan already feels pretty explicit and low-level from day one, so i'm wondering if it is basically stable in that sense, or if the recommended way of writing Vulkan code could still change a lot over the next 10 years.