Go full robot: “Estimated timescale for the completion of this task?”. I doubt they’ll get annoyed at that, might just find it funny, or weird. no, definitely wierd.

Yeah the sub-culture that had star trek as one of it’s major contributors is surprisingly welcome to diversity. I wonder why that is? \j

I think it’s simply the case of the media that nerd culture grew out of was very welcoming to diversity, setting the standard for the entire sub-culture. I mean DS9 had a same-sex kiss in the 90s, with Dax a gender-swapping alien. I doubt that’s a coincidence.

My logic was simply: I need a buffer that is only initialised once no matter how many times the function is called. statics are initialised at program start so they seemed like a good fit. and since I wasn’t planning for the function to me called multiple times simultaneously it seemed like the UB didn’t matter. (which I think was correct)

Thanks! That’s exactly the answer I was looking for.

The premature optimisation quote at the end of your blog post is very relevant to me. I try do find the most efficient way right off the bat so very frequently the first questions I have in a project are like this one. Which in turn lead me to understand the underlying basics, which make me want to implement those basics myself, which sends me down a spiral to wanting to write my own kernel. All the while the project I started with gets forgotten, until I pick it up a month later and the whole thing starts again.

Maybe I should just try and learn C… or zig. And try and hold myself to the higher quality standard they demand. Especially since it feels like I’m doing that already.