signpost[asciilifeform]: congrats awt, fine place to have modularity.
awt[asciilifeform]: $ticker btc usd
asciilifeform: hmm bot awol?
phf[asciilifeform]: http://logs.nosuchlabs.com/log/asciilifeform/2022-07-30#1112646 << i could never quite grasp the point you're making here. lisp machine will have some kind of datastructure to represent e.g. image, usually involving an nxn array, which then can be dumped onto filesystem as a fasl without the need to serialize to png. but h
phf[asciilifeform]: ow does that work with cross system? at some point you have to read/write a serialization format, and then encoding standards come in as an efficient way to transmit (and store) large data frames
phf[asciilifeform]: or is the idea that encoding algorithm should travel in the container?
phf[asciilifeform]: now that i'm asking a quesiton, i feel like i remember you elaborating on it, possibly as a result of my prompt in the past
phf[asciilifeform]: and if it's the later, would you not be moving the “format” question from one bucket to another, no long have a png, now have a “webassembly” vs “jvm” or whatever
dulapbot: (asciilifeform) 2022-07-07 phf: but also at this level of thought shaping you're basically running into the fact that there's tons of existing protocols and solutions that could be used or shoehorned or influence your decisions or whatever, and simply saying "i don't care, i'm just using pest" is a kind of gordian knot cutting