07-07-2024, 12:29 PM
Update from 1 week later of full time Vulkan programming (and still far from anything playable in sight), I actually start to enjoy Vulkan.
So much so, I just bought the Vulkan Programming Guide book in both English and Japanese (both 2nd hand though).
The Japanese one arrived today, the English one is expected to arrive tomorrow.
The reason why I enjoy Vulkan now is because even though there's tons and tons of boilerplate (currently roughly 2000 lines of code, barely any of it goes to actually rendering stuff on the screen), it really teaches you how the GPU, CPU, and RAM actually work in the process, and you'll realise really quick how much OpenGL has been holding my hand all this time by providing almost everything for me just so I can render stuff to the screen as soon as possible.
In Vulkan you actually have to set everything up from the ground up, kind of akin to how GUI programming used to be in the very early days of Xorg back in 1984, when it could take months before you could even show an empty window on the screen.
It's not the best API to work with if you want to make a quick buck real quick, and probably not a good idea to teach it in a single semester (I'd recommend 2 to 3 semesters for that), but it really is the best API if you want to build an engine from the ground up and learn how the computer exactly works, and I really enjoy this whole process.
For those who are wondering, I'm using this playlist, I found it to be really good and he explains quite a lot of things in depth to make you better understand various concepts, I downloaded the entire playlist to my local machine using yt-dlp, because 1) I can watch in 1080p without having to connect to the internet, and 2) YouTube sucks.
The only thing I dislike about this guy is that at one point he completely rewrites everything off-camera, and the only way to get in line with his new code is to just copy/paste from his Github repository, which is pretty unhelpful.
I've read through a few pages of the Japanese Vulkan book while riding a train, so a few more episodes to go, and I'll just transition to the book instead.
So much so, I just bought the Vulkan Programming Guide book in both English and Japanese (both 2nd hand though).
The Japanese one arrived today, the English one is expected to arrive tomorrow.
The reason why I enjoy Vulkan now is because even though there's tons and tons of boilerplate (currently roughly 2000 lines of code, barely any of it goes to actually rendering stuff on the screen), it really teaches you how the GPU, CPU, and RAM actually work in the process, and you'll realise really quick how much OpenGL has been holding my hand all this time by providing almost everything for me just so I can render stuff to the screen as soon as possible.
In Vulkan you actually have to set everything up from the ground up, kind of akin to how GUI programming used to be in the very early days of Xorg back in 1984, when it could take months before you could even show an empty window on the screen.
It's not the best API to work with if you want to make a quick buck real quick, and probably not a good idea to teach it in a single semester (I'd recommend 2 to 3 semesters for that), but it really is the best API if you want to build an engine from the ground up and learn how the computer exactly works, and I really enjoy this whole process.
For those who are wondering, I'm using this playlist, I found it to be really good and he explains quite a lot of things in depth to make you better understand various concepts, I downloaded the entire playlist to my local machine using yt-dlp, because 1) I can watch in 1080p without having to connect to the internet, and 2) YouTube sucks.
The only thing I dislike about this guy is that at one point he completely rewrites everything off-camera, and the only way to get in line with his new code is to just copy/paste from his Github repository, which is pretty unhelpful.
I've read through a few pages of the Japanese Vulkan book while riding a train, so a few more episodes to go, and I'll just transition to the book instead.