@RustyCrab probably because theres samples of code like for (int *i=p,printf(char*,...),puts(char*);i<n;i=((int(*)(void*))i)(&i)) that some boomer wrote in 1999 or something
@Inginsub@kirby@ademan speaking of segfaults, its kinda surprising that no programming language runtime i know of logs function calls, so when you mess up the stack and wind up with a borked stack trace you can't really debug it, and logging function calls solves that, like in cosmopolitan libc https://justine.lol/ftrace/
@syzygy >defends OpenBSD but not MacOS even though fucking MacOS is less restrictive >has trillions of ideas for security theater "mitigations" enough of your hypocrisy, please
@kirby@s8n FreeBSD is much more unified than Linux distros, musl and glibc already disagree on some headers too, like arch_prctl, god knows what other libcs do
@syzygy thank you for fending me off with random jumps and trashing my pipeline with your ejaculation matter, i need less useless branches in my instruction cache, not more
@s8n i aint, its my old experience with the pile of trash in question when i tried to port some shit to OpenBSD because i wanted even basement /g/tards to use it, but there was practically no way to do it on OpenBSD, but i could do it on a MacOS VM and i had the displeasure of remembering the whole bullshit i went through while snorting roofies its just as frustrating as trying to develop on Windows Server
You're not your thoughts, you're not your brainYou're just the character you've madeIt's not the way that you were raisedOr what the advertisements sayAnd something tells meYou prefer to be sitting there flipping through all these old issues of peopleWell that's our time, see you next week