vulkan-guide VS DiligentEngine

I totally agree, and so do the people working on it as well as some of the volunteers who write tutorials.

There's an ongoing effort to create beginner friendly introductory material which was discussed in the recent Vulkanised conference. And an effort to make a better documentation site that's easier to browse than the specification.

On the volunteer front, there's a Vulkan 1.3 -based introductory tutorial (work in progress) over at https://vkguide.dev/

I think there should be a Vulkan tutorial that doesn't start with the boring stuff of initialization and window creation. It's stuff that you write once and forget about, and nothing particularly interesting happens in it.

Looking at my hobby project, excluding the boring stuff (which is reusable), a "hello compute" example is around 100 LOC and a "hello triangle" around 120 LOC. GLSL shader sources included.

Maybe someday I'll get around to writing a "learn Vulkan the hard way" blog post with examples.

Also, use https://vkguide.dev/ rather than vulkan-tutorial.

Once you're beyond the "introductory" phase, resources become more specialized based on what you'd like to learn -- there are Vulkan tutorials like https://vkguide.dev/ which will teach you the API and also give a bit more insight in how modern GPU hardware is structured, there are books like the "GPU Zen" series that do deep-dives on specific techniques, and there are tons of recorded GDC and SIGGRAPH talks on interesting new techniques. :)

Personally, I'm a hands on learner who actually wants to use this stuff in my career, so I'd recommend these tutorials: https://learnopengl.com/ https://vulkan-tutorial.com/Overview https://vkguide.dev/

vkguide teaches some good practices regarding code/renderer structure, but I'm afraid it doesn't go as deep as you'd like. It's certainly deeper than most other tutorials, though.

https://vkguide.dev/ This is my favorite.

Neither Apple nor Microsoft want any usable multiplatform graphics API. For this reason, none of them delivers such a thing.

If you want a multiplatform graphics API, you should use a library which implements such API on top of these native OS-specific APIs.

I have good experience with that one: http://diligentgraphics.com/diligent-engine/ I’ve used it couple times on Windows with D3D12 backend, and on Linux with GLES 3.1 backend.

Diligent Engine: They say their engine is the successor of bgfx, but I'm not rly into that topic.

Diligent Engine. A Modern Cross-Platform Low-Level 3D Graphics Library and Rendering Framework Tweet.

Read other people's code (I recommend modern small to medium sized github projects, because large ones can be overwhelming) or else you will forever stay in your bubble of how things are done. For example, I had learned a thing or two by using (and code browsing) diligent engine's source.

Diligent Engine

I'm not speaking out of my ass, either, I have very actively followed low-level development being done towards open-source engines such as Diligent and Wicked. I personally am a contributor to the latter engine, as well. It is baffling to me that independent developers don't support this platform.