BingoBoingo: asciilifeform: There might be the potential for something lulzy there, but this is looking fairly mundane to me.
BingoBoingo: Yes it's an insane situation, but can you rewrite the copy to hit particular points of wrongdoing? Don't worry about urls, I've got text extracted from the pdfs.
BingoBoingo: asciilifeform: Aite, awk is starting to make some sense. I'm going to report where I've made it on the automation in #trilema-hanbot and get outside to stretch the legs
snsabot: Logged on 2020-02-18 01:41:26 asciilifeform: BingoBoingo: i'm at the dc again, fighting an apparently cursed raid card ( my box, not customer's ftr )
snsabot: Logged on 2020-02-18 03:11:34 snsabot: Logged on 2020-02-18 01:41:26 asciilifeform: BingoBoingo: i'm at the dc again, fighting an apparently cursed raid card ( my box, not customer's ftr )
shinohai: I meant to comment on BingoBoingo 's India takedown Qntra piece.
snsabot: Logged on 2020-02-12 23:32:26 asciilifeform: curiousd0g: you know that proxy co.'s are honeypots , yes ? (is this term familiar?)
shinohai: " unless required by law" .... so subjective.
snsabot: (trilema) 2017-03-01 asciilifeform: what are ~all~ of the places where A has the ecstasy, but B does the laundry, where A!=B
snsabot: (ossasepia) 2020-02-18 BingoBoingo: diana_coman: If it's not too late, I would like to pledge as a page. This weekend as I turned 34, I was struck by terror as I pondered
what exactly is inside my veins. Dread left me paralyzed. For years I've been trying to conquer my shortcomings as an independent, and I have failed.
shinohai hearls the distant sound of safety bell tinkling over grave from previous thread.
verisimilitude: On the topic of those who lead and those who follow, do you've any thoughts regarding that Common Lisp Style Document I wrote, asciilifeform?
verisimilitude: I considered pointing that out explicitly; it's still in-progress, so I'll explicitly note the case is for display purposes only.
verisimilitude: Interestingly, I put a space after the comment introduction in APL and Ada, but not Common Lisp. I write more comments in those two than Common Lisp, as well.
verisimilitude: As for mechanical enforcement of this style, I'm too lazy to dig around to accomplish that is one way to phrase it. The mind and the body are both unwilling here.
verisimilitude: Is there anything important you believe I've omitted, asciilifeform?
verisimilitude: Sure, I don't disagree. Someone in my group wanted a good style guide and, lacking writing ideas, I thought I'd write one distilling my thoughts.
verisimilitude: Besides, the guides which do exist truly are poor, in my eyes.
verisimilitude: I yearn to begin work on my own Common Lisp implementation this year, but it will have its own goals reflecting mine.
verisimilitude: I want it to be memory efficient, rather than time efficient.
verisimilitude: So, making it use as little memory as is reasonable is the main goal, as opposed to making it fast. I'll stress I won't be cheating by implementing DISASSEMBLE and friends as naught, among other things.
verisimilitude: Regarding what else you wrote, I'm usually rather uninterested in what others are working on or what's popular. I'm currently learning REFAL, because I found it following links on your website lately, but were I only concerned with what's available or popular or whatnot, I'd discard this neat language without a second thought, and be worse for it.
verisimilitude: That's another way I won't be ``cheating''; I want a full machine code compiler, along with an interpreter.
verisimilitude: It would be memory efficiency without eschewing other nice things.
verisimilitude: Anyway, I'll probably only start on the Common Lisp side of things, this year. One aspect of macroexpansions under the popular implementations I vehemently dislike is how they don't expand to pleasant Common Lisp.
verisimilitude: You want to see what LOOP, say, expands to and you get calls to what may as well be LOOP-PACKAGE::IMPLEMENT-THE-SPECIAL-LOOP-THING-DONT-TOUCH-FUCK-YOU.
verisimilitude: Now that I mention this, I should add this macro note to my style document, certainly.
verisimilitude: Yes, but I think it can be walked better than it currently is.
verisimilitude: By the by, can you guess why it's a ``style document'' and not a ``style guide'', asciilifeform?
verisimilitude: I've not written a compiler to machine code yet, no, but I've written other compilers.
verisimilitude: Architectures I don't like or care for is what the interpreter would be for.
verisimilitude: My machine code work is still preoccupied with that development tool I've been lazily working on. I'll probably work on a MIPS targeting, next, once I finish that which I'm currently focusing on having working and well.
verisimilitude: The Intel architecture isn't even suited to assemblers, so it's not a target I intend to aim at.
zeder: there's obviously a lot of backstory here that I've missed, but it's not immediately clear to me what "Intel arch isn't even suited to assemblers"
verisimilitude: In considering writing a development tool for Intel architectures, there's too many instructions and variations thereof for my model, but even an assembler is unpleasant to use, due to the sheer number, prefixes, and other such things. It's my understanding Intel has a library specifically to make it easier for others to write an Intel assembler, because it's so complicated.