so much better than google docs/slides.
| website | http://gpfault.net/ |
| github | http://github.com/nicebyte |
| bluesite | https://bsky.app/profile/nicebyte.bsky.social |
| website | http://gpfault.net/ |
| github | http://github.com/nicebyte |
| bluesite | https://bsky.app/profile/nicebyte.bsky.social |
@pythno @nicebyte That's https://www.howtovulkan.com
It's supposed to show how to do Vulkan rasterization in 2026.
RE: https://hachyderm.io/@ekuber/116030329406582341
really makes you think
VK_EXT_descriptor_heap proposal is a good read.
vulkan has come a long way, to the point that if you use all the modern improvements, it looks almost nothing like what came out in 2016.
dynamic rendering and unified image layouts were my favorites as obviating the most annoying (and often pointless on modern hw) parts of the api. this one is the best though, i've always hated descriptor sets.
https://docs.vulkan.org/features/latest/features/proposals/VK_EXT_descriptor_heap.html
writing this was partly a byproduct of thinking a lot about how applications interface with OS.
i like the fact that Linux syscall abi is stable. Kernel's good, but userland shits the bed: libc, dynamic linker and threading are all interdependent. you can talk to the kernel directly but the second you need a dynamic library it's game over. libc infects everything, and is the reason that being able to run the same Linux binary on two different computers is not a given.
GO HOME, WINDOWS EXE, YOU'RE DRUNK (in which we use wine in ways god did not intend) https://gpfault.net/posts/drunk-exe.html