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

@wallhackio i can’t stop drinking oil

@vaporeon_ https://en.wikipedia.org/wiki/File:Chicxulub.ogg

the mysterious bug ​

my youtube recommendations are full of decade+ old furry memes lately and i kinda love this

@vaporeon_ it really is so cool that girl creachers

@vaporeon_ the fishcat

@coriander @wallhackio she bumbly

@wallhackio the java stream api uses streams. the unix file api uses streams. these are the same kind of data structure. that is my point. the APIs and the furmer being a generic data container (whereas unix streams are all of char) are what are diffurent

@wallhackio https://media.githubusercontent.com/media/sarabander/sicp-pdf/master/sicp.pdf#section.3.5

@wallhackio streams are old

@wallhackio it has literally always been pawsible fur a file to spew an infinite amount of data and the core I/O APIs have always been able to handle this

@wallhackio you call it fad-chasing but unix I/O has literally always been stream-based

@u2764 “not modern web development (derogatory)” is not exactly a meaningful criticism to me, is my point

@u2764 well modern web development is shipping 50 billion tons of client side javascript with every request so

having two entire coreutils in the new LTS’s base system is a hilarious situation to end up in imo

there is something of a delicious irony in Ubuntu wanting to move to a Rust based coreutils reimplementation fur security reasons and then hiring a security firm to investigate its codebase and discovering 130 security bugs and also that cp specifically is subject to many open race conditions with security impacts