🌾 ivan 🌱 @ivan@coolkids.house

Стимлянная Хамоника (1968)

https://www.youtube.com/watch?v=yVmw3ZhdzEs

using goto is like embedding a fun little easter egg hunt in your code

imho all code should be as funny as it can be without compromising readability and structural integrity. if some poor asshole has to ever read it at least they'll have a chuckle

every time i use goto among modern templated C++ code, i let out a little chuckle

@helvetica did you see this? lol

https://twitter.com/kcimc/status/1634334907790135298

what is everyone's setup for versioning game builds?

@mcc in my framework, i just have a templated buffer struct that wraps around a C++ struct that handles all of that, so all you do is just update your CPU data and call update() on it and it does the GPU memory update. if you have multiple frames in flight you also need to keep a separate device memory for each frame, so it has to handle all of that.

@mcc you keep a handle of a VkDeviceMemory which is bound to a descriptor set at a specific location, then you just map it to CPU memory, copy it and unbind when you want to update shader data.

@mcc ah i see, well not sure what the best approach then. fwiw in C, you don't update descriptor sets usually, you just map memory for a buffer in the set, copy it and unmap it.

@mcc Ah I see. I find the binding # approach quite a bit better in that you can just map a CPU struct to shader memory and then just set stuff in the struct directly without ever dealing with strings (though there is some memory alignment stuff to keep in mind).

@mcc you shouldn't be doing it by name, the block approach is so you can map CPU memory to shader memory directly

asked GPT4 to generate C code for a simple pong game that runs in the terminal and it generated it on first try along with instructions on how to install libncurses and build it

the first time your game AI beats you at your own game feels so good