Piero Bosio Social Web Site Personale

ASCII characters are not pixels: a deep dive into ASCII rendering. https://alexharri.com/blog/ascii-rendering

@vitaut @jsbarretto Although this makes me realize I've never actually checked the spec wrt the semantics for stack/automatic storage duration variables for the self-referential initialization pattern (it's hard to see a use case) but I guess it's still alright?

@vitaut @jsbarretto The interaction with captures is cursed but you can do stuff like

Node n = {.value = 42, .next = &n}

in C to statically initialize self-referential pointer-based data structures. The more interesting case is something like

Node n[] = {{.value = 1, .next = &n[1]}, {.value = 2, .next = &n[0]}}

where you effectively get the linker/loader's relocation engine to deserialize cyclic pointer-based graphs. For statics you can also just extern declare the variables.

@dotstdy Especially if you're doing the pixel at a time stuff it's hard to see how ticking gameplay at higher than 60 would be very useful? You can always substep specific systems that are sensitive. Although I guess if your goal is to reduce input latency, yeah.

@jplebreton Extremely clunky in some respects, and I don't think the almost Dragon's Lair like instant-death room by room design was ideal, but man did it feel special at the time.

@jplebreton That reminds, did you hear that apparently Mikami was told by Capcom executives not to acknowledge Alone in the Dark as the (extremely obvious) influence on Biohazard/Resident Evil due to fears of lawsuits? He only came clean about that much later. It's just incredible how far ahead of its time Alone in the Dark was.

@wolfpld Even if it affirmed all my values and cultural priors, I still wouldn't find it usable. I still use it in read-only mode maybe once a week via nitter.net in order to check some specific things, and even without the algorithmic feed it's 95% slop and engagement farming, most of it by obvious bots.