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

@vaporeon_ i opened Pachli to edit the post and immediately typed another capital W and just had to sit there fur a second and accept it befur fixing the typo fur real and sending it

@vaporeon_ sigh lol

the overwrite script from The Unix Purrogramming Environment is one of those things that i never bother to add to my PATH and then keep regretting in the occasional moments where it’d be useful to have

@wallhackio ooh

@vaporeon_ anti-repurrted

@wallhackio also, you did tell me you read the parts of the book that would have covered the infurmation i called you on not learning. so

@wallhackio i did not call you out on the public timeline btw

@wallhackio you’ve given me a three month timeline to accomplish something extremely funny in a petty way, nice job

@wallhackio bumby are you thinking of the sockets purrogramming book. that is a diffurent book from what i’m talking about

@wallhackio it’s not large…

actually this is a callout post now. @wallhackio i KNOW you’ve read The UNIX Programming Environment so you have no excuse fur not knowing this

@vaporeon_ yeah you get it

@vaporeon_ i don't know!!!!!!

@wallhackio you realize a benefit of “beautiful functional purity” is that the design ethos is extremely conducive to thread safety, yes?

@wallhackio you did not learn functional purrogramming from haskell lol

@vaporeon_ i got excited this past week by thinking of an excuse to write a CGI script in trivial C and then was disappointed to realize i could just do it entirely in NGINX instead, and more simply too

i was complaining about how i once helped my ex write a script in fish and got snagged by fish running pipelines synchronously and did not even remotely expect that bumby would just expect a shell to work that way in the furst place

@vaporeon_ you generally have the intuitions i expect of a creacher who’s been daily driving unix systems fur a long enough time

@vaporeon_ no