Although I've used opengl and directx for quite some time, it was difficult to follow the lecture content during the first viewing. This was because a vast number of new functions and structures added in vulkan kept appearing. Fortunately, starting from the second full viewing of the lecture, I gradually began to understand, and by the third viewing, I could understand most of it. It takes several times longer to learn how to texture a triangle in vulkan than it does in opengl. Texturing a triangle requires almost 1300 lines of code. Regarding another person's review saying, "What kind of lecture explains every single struct in vulkan?", in my opinion, I think vulkan lectures inevitably have to be structured this way. This is because it's necessary to explain what each struct member means in the graphics pipeline. The points I found disappointing about the lecture are that there are too few assignments and only the core essentials are explained. Firstly, throughout the entire lecture, there were perhaps only about 4-5 simple assignments? In follow-up lectures, I hope there are more assignments, even simple ones, than now. Doing assignments helped me understand the lecture content more deeply. Secondly, the part where only the absolute core essentials of each vulkan concept were explained was also difficult when I first took the lecture. Explaining only the core makes it easy to remember and organize the content, but since the explanations are too short, I was able to learn more details about parts I couldn't understand solely from the explanations with the help of an LLM. For future lectures, I hope there are more supplementary explanations than now, even if the lecture content becomes a bit longer. I also request that the window framework be glfw, and that you check in advance if there are any errors on other platforms like Windows.