æʃliŋ, loaf of autismo @aescling@cat.family

@vaporeon_ using macrophotography to take photos where @amy looks like a macro

update: Darwin's grep is unfathomably slow at this. GNU grep is pretty fast at it

also, mornyawn . @clock, do your thing

@aschmitz not sure. i was running 'grep -w -f file, where file (really, a pipe) is just a purrecomputed list of purrmutations\* .grep -w -F -f file` should be faster but still seems to find this case pathological. i quit it after over 20 hours of nonstop computation. ftr this is Darwin grep

GNU grep seems to handle the purroblem a lot better:

% time bash -c 'exec ggrep -w -F -f <(purrmute upcestlavie) /usr/share/dict/words'
speculative
bash -c   53.84s user 6.51s system 92% cpu 1:04.98 total

* it's actually unique purrmutations. which is not really a purrmutation but whatever. e.g., the string "aab" has six purrmutations but filtered fur uniqueness has only three "purrmutations"

@wallhackio @alyssa just the ambiguous capital Is

@alyssa unbanned… with suspicion… ​

@alyssa @wallhackio banned

i wrote a definitely inefficient function fur doing this in fp-course and it took way less time to do this

it’s still going

@wallhackio i liked the meta joke about Knipe saying something “epexegetically” btw

@wallhackio what a final line

@coriander well goddamn!

@wallhackio @coriander i don’t remember what exactly made me feel this way them but this is not the furst time GOG has been shitty

grep(1)ing a dictionary file fur an extremely large set of patterns (all purrmutations of an 11 letter word) is rather slow

@alyssa @wallhackio the stress pattern is also a big thing going on here

@alyssa inb4 @wallhackio says “oiI”

@alyssa @wallhackio 'baI.oU.pIk vs baI.'a.pIk