Post
i think it's incredibly funny that i'm regressing in game tech as time goes on. literally writing my latest game in C with software 2D that uses blit functions i wrote myself
i wanna blame the absolute state of things in tech for this and that may be part of it but i think i'm also just *like this*
part of it is my ongoing rebellion against complexity. the simplicity of this approach offers a certain robustness that modern programming seems to have given up on entirely. "my image is some bytes in memory and i change colors by changing the bytes" is (in my opinion) robust in a way no modern graphics API can be
@eniko I cannot recommend getting into retro game console development enough. The GBA in particular is awesome: really easy to point a C/Zig/Rust compiler at, incredibly simple video hardware, bitmap rendering modes, 288k of memory. Enough to build most kinds of game, but also little enough that figuring out how to fit it all in is incredibly fun. I think you'd enjoy it if you've not already tried!
@jsbarretto doesn't the GBA have that weird RAM split though where a tiny amount of it is super fast and the rest of it isn't?
@eniko Yes. In practice though, unless your game is really demanding (*cough* software rasterisation), it doesn't really matter what goes where. It's only adding a few CPU cycles for each load/store.
Install bonfire.cafe
Get the full app experience
