log☇︎
128400+ entries in 0.074s
ben_vulpes: mod6: it's not a personal attack, i disagree that i agreed that v.pl was doing the Right Thing in leaving ~/.gnupgtmp hanging around
asciilifeform: trinque: barf all you like, the d00d nearly made a working cuntoo
trinque: gabriel_laddel: honestly why should anyone give a fuck to improve you.
asciilifeform: gabriel_laddel: this is good to hear.
asciilifeform: gabriel_laddel: and call it what you want, but imho it'll be moar appreciated as linux distro, than to label 'lispm'
gabriel_laddel: aite. but ftr you can ASSIGN me stuff that I will do. eg, leaving CA, finding job. Eventually was convinced.
mod6: i hope you're not trying to say that im simply making this up
mod6: my vtron has been discussed very much over the last 2+ years. i remember many disucssions where rules popped out. ☟︎
mod6: <+ben_vulpes> logs save us from the "but i thought we agreed" floppy meatsack memory. << i feel ya. if you wanna help me dig, that'd be awesome.
ben_vulpes: mod6: make a disposable tempdir like stans original and my port. i don't know whence this 'agree', stan's original was clear enough.
mircea_popescu: asciilifeform which part of trilema is plaintext ? the part where it says fuckyoui or the part where it says fuckyou((norly)) ?
mod6: and the details of what the change is to do are clear so I can implement them as such.
a111: Logged on 2015-12-25 23:10 asciilifeform: because, again, the whole 'plain text' jwzism and the attendant retardation. somehow 'lines' are a thing.
ben_vulpes: logs save us from the "but i thought we agreed" floppy meatsack memory.
mod6: i know, i haven't had a chance to look yet.
ben_vulpes: mod6: you gotta quote chapter and verse from the logs to support "outcome of that discussion".
mircea_popescu: and there is no such thing as fucking "plain text"
asciilifeform: it's the only thing that works.
asciilifeform: and of 'plain text' idea.
asciilifeform: it does however mean letting finally go of the vt100.
mircea_popescu: as i say -- i see no way out here ; we'll end up with the v-code + blog-commentary ostrich-camel and god help us./
asciilifeform: it's the gordian cut.
asciilifeform: sorta why i favour the structure-editor and store-EVERYTHING-as-sexprs approach.
mircea_popescu: this is the problem. you can't disagree with my theory and i have no practical solution for your pain.
mod6: <+asciilifeform> second , as in the case discussed in the thread, if a run aborts, it creates a mine for next run to step on. << try to realize that this is on-purpose. im certain that we've had this discussion before and what exists is the outcome of that discussion.
mod6: <+asciilifeform> no good. first of all suppose there are 2 concurrent runs of the vtron ( say this is a cuntoo pressing itself ) << yeah, concurrent runs of my vtron are a no-go.
mircea_popescu: it's actually SO BAD that people go re-implement the same damned X thing for the 90th time as a substitute of commentary ; and nobody looking understands wtf that is.
gabriel_laddel: asciilifeform should I even bother stopping in then?
mircea_popescu: until this is resolved, the perennial results will repeat.
mircea_popescu: in any case, here's the logic : the proximate cause of the failure of "computer science" to amount to 0 (not epsilon, 0) since its inception is strictly due to poor treatment of comments as 2nd class item in code. ☟︎
mircea_popescu: if that's what it actually takes, yes.
mircea_popescu: asciilifeform somehow you jump from "my printer is shit, doesn't work properly" to "either magic number or throw out printer" ☟︎
mod6: asciilifeform picture scene from film 'idiocracy', where hero gets 'his name', 'Not Sure', tattooed on forehead << his arm, but yeah, great movie.
asciilifeform: mircea_popescu: rails -- have gauge. and spacetime itself appears to come with 'magic #s'.
mircea_popescu: asciilifeform anyway you turn it, the concept of magic number's not defensible.
mircea_popescu: except that day will be rather sooner than that.
asciilifeform: so far the folx who code on paper, wrote ffa, and the folx who wrote on display -- wrote what.
asciilifeform: 'do from cause, not purpose' necessarily includes not giving rat's arse re 'what will lose out to one day when sun burns out'
mircea_popescu: in this case, atavism just loses out.
asciilifeform: in the end man can lose out to cockroaches also.
mircea_popescu: there's a reason your father+grandfather haven't amounted to as much of a fart as a workable os.
mircea_popescu: asciilifeform and write too little of them and too sparse and lose out to the other variant in the end.
asciilifeform: i'ma carry right on wrapping comments to 80, like father and grandfather did and like the gods intended.
mircea_popescu: anyway, there's no possible solution here ; i expect the defacto result will be that patches will consist of code, wrapped 80, including 0 comments, plus blogposts, consisting of commentary, with some haphazard code reference.
ben_vulpes: want to corroborate what appear to be facts before plowing down a possibly retarded path though
a111: Logged on 2018-01-05 13:41 asciilifeform: diana_coman: 'best thing is never to have programmed at all' or how did socrates put it.
mircea_popescu: asciilifeform if true, this is == "code is not worth either writing or reading"
asciilifeform: ( whynot, is not a bad question, it reduces to the absence of a solution to the tednelson problem -- how to point into a structure unambiguously, other than by line # ) ☟︎
mircea_popescu: not the other way round.
mircea_popescu: "we are incapable to reflow and here's a magic number instead" differentiates monkey from man
asciilifeform: i'ma disagree that the use of paper is 'bad habit'
mircea_popescu: code and comments do not, actually mix ; the fault is entirely of bad but entrenched habits of code writers.
mircea_popescu: seems atm we uncovered the deep limit on literate code.
a111: Logged on 2018-01-05 09:56 diana_coman: which is perfectly fine with me for code; it's still grating for comments and I'm not sure how this will resolve, it sort of pushes comments out of code (to a place where one can read them as text not as code-which-they-are-not)
mircea_popescu: http://btcbase.org/log/2018-01-05#1764893 << yeah tis a problem ;/ ☝︎
asciilifeform: or for that matter any record kept of old instructions , that the thing could jump to ?
ben_vulpes: hey man i only figured out how conditionals worked today
asciilifeform: ben_vulpes: you tell me
ben_vulpes: asciilifeform: is there some way of doing iteration with the opcodes from ch4 ?
asciilifeform picture scene from film 'idiocracy', where hero gets 'his name', 'Not Sure', tattooed on forehead
mircea_popescu: in other lulz from the road, "nombre ?" "credible" "apellido ?" "justin".
ben_vulpes: then at that point the historical perspective was obviously necessary and i've simply never seen modern arch's as anything other than complexity madness in search of itty bitty performance gains on systems nobody can actually reason about
ben_vulpes: i only started thinking about compute because of bitcoin, and shortly after i started thinking about it in earnest (like maybe a month, six weeks something like that) you showed up in #b-a and /even at that point/ were talking about eg trinary circuits and computing fabric
asciilifeform: ( upstack : dma, interrupts, pipeline, instruction reorderer, 'hyperthreading', multiple buses, 'bridges' -- all are epicycles ( hey mircea_popescu ! ) from vonneumannism , where instructions 'push' (unrelated to stack concept) outputs, rather than 'pull' inputs as they oughta ) ☟︎
ben_vulpes: i've never been burdened with the "This Is How Things Are" of the c-machine
ben_vulpes: it all strikes me as so very silly on the surface but i have a weird lens of not having thought about any of the related shit until ~2013 and even then only through republican eyes
asciilifeform: on the other hand, pipeline idea per se was a mistake; same kind of failure to invent dataflowism as dma
asciilifeform: ( on vliw, there was a pipeline, but proggy was expected to fill it 'by hand' . a kind of 'stick shift'. if a sub-instr stepped on another's toes, it was a eggog, like div0 is on x86 , abort . )
asciilifeform: bbbut noooo, gotta reorder, because Only A Terorrist Would expect microshit to write sane compiler... ☟︎
asciilifeform: semantics-changing optimization belongs in ~compiler~ (if even there), not in iron.
ben_vulpes: iphones apparently vulnerable to SPECTRE too, hilariously
ben_vulpes: yeah but fuck them in particular
asciilifeform: it's a gnu coreutil. so theoretically yes
ben_vulpes: is mktemp widely installed enough to be used here?
asciilifeform: ( make a string out of /dev/random crapola + current epoch time, say ) ☟︎
asciilifeform: you can fix the second by erasing at the beginning of a run. but not the first.
asciilifeform: second , as in the case discussed in the thread, if a run aborts, it creates a mine for next run to step on.
asciilifeform: no good. first of all suppose there are 2 concurrent runs of the vtron ( say this is a cuntoo pressing itself ) ☟︎
asciilifeform: how do you create the ~name~ of the dir
mod6: the keyring that gpg needs to run
mod6: i don't have a chance right this moment to do that, will look tho when i can
mod6: now, i can add an attempt to remove the thing before we even begin main(), but i thought we had discussed this. i'll have to dig up the old thread.
mod6: and if you ^C the thing mid-way through the execution, you'll never hit remove_tmpdir
mod6: <+asciilifeform> mod6: an aborted run of vtron should not be able to put a caltrop for subsequent run to die on. this is imho elementary.
mod6: im getting pulled off here... i'ma try to circle back to this but...
ben_vulpes: ah over is the key!
asciilifeform: let's quote ftr : 'Creates a temporary directory in the most secure manner possible. There are no race conditions in the directory’s creation. The directory is readable, writable, and searchable only by the creating user ID. The user of mkdtemp() is responsible for deleting the temporary directory and its contents when done with it.'
asciilifeform: however the external 'tempfile' item, made gensymtronic dirs. so this never became a headache.
asciilifeform: did not attempt to catch ctrl-c or any other signal.
asciilifeform: gpgtmp = tempfile.mkdtemp()
asciilifeform: well, let's reread http://trilema.com/2015/no-such-labs-releases-v-for-victory then : ☟︎
ben_vulpes: mod6: i don't actually recall any agreement on the topic, you did yours one way and i another, and i cannot recall how asciilifeform's original handled this
a111: Logged on 2015-11-05 02:08 asciilifeform: -- a unique thing that never was and never will be again.
ben_vulpes: mod6: http://btcbase.org/log/2015-11-05#1316693 is what i dig up on the topic ☝︎
ben_vulpes: had to go beat self with everything i was never beaten with starting in my early twenties when the republic kicked off
asciilifeform: mod6: an aborted run of vtron should not be able to put a caltrop for subsequent run to die on. this is imho elementary.
mod6: im pretty sure we all had this discussion once upon a time, and it's only doing now, what we agreed to do before. I can go and dig for that.
asciilifeform: ben_vulpes: odd! are they so rare today ?
asciilifeform: esp if it gets in the way of a subsequent run
mod6: otherwise, my vtron handles the creation and deletion of that .gnupgtmp dir on its own.