Sherclod Holmes @wallhackio@cat.family

@vaporeon_ the answer is "it's complicated": https://pmc.ncbi.nlm.nih.gov/articles/PMC11427400/

@vaporeon_ yeah you could do something very similar in js

good "morning"

@vaporeon_ I haven't carefully scrutinized it but I like the approach in principle

Personally I prefer readability over concision as long as the code isn't performance critical (which is most code). So bigger code size is rarely an issue for me

@vaporeon_ @monorail I give up

@vaporeon_ @monorail fuckin hell

the message from deep space is currently humbling me

@monorail I did more thinking about this while I was supposed to be playing Deltarune and am now preferring:

let idx = currentSignal.length;
while(i < matches[0].length && matches[0][idx] === matches.at(-1)[idx]) ++idx;
let i = idx - currentSignal.length;

@cam I've never had any experience like this with a cyclist so I wonder if this is just a California thing

@cam maybe cars were a mistake

@cam I hope they also stub their toe daily

To the driver that honked at me while I used the crosswalk while I had right-of-way, I hope you stub your toe every day for the rest of your life

@root @monorail i need to learn how to read

@monorail this is currently beyond my pay grade and I would have to do research to properly code review this so I really just have to take your word for it on your evil code

@monorail ah shit I forgot to account for the linear flow of time again

@monorail I have a very poor understanding of how the browser actually handles animation so the fact that this works at all is kind of blowing my mind

@monorail this really evil and cool and cursed but it is also probably unnecessary: https://developer.chrome.com/docs/css-ui/animate-to-height-auto

@monorail // This next part is a bit cursed, and it took me a long time to figure out.

deeply foreboding comment