log☇︎
17100+ entries in 0.308s
asciilifeform: this is entirely separate problem from 'i don't know how a 6502 worked'
asciilifeform: esthlos: satan himself doesn't know what typical x86 pc does with 99% of its time.
asciilifeform: the gprbuild thing hasn't changed since ch1, also, and i dun expect that it ever will ( unlike makefiles, these dun need to )
a111: Logged on 2017-11-29 01:41 asciilifeform: funnily enough adacore itself publishes a great many cut-down runtimes for various embedded boxes, e.g. https://bitbucket.org/tkoskine/embedded-arm-gnat-rts/src . BUT they are not usable: 1) there is -- quite deliberately -- not one targeting conventional userland linux 2) none of them support exception handling, which wouldn't be a problem except that ALL BOUNDS CHECKS ARE EXCEPTIONTRONIC
a111: Logged on 2018-01-07 09:01 mircea_popescu: sn't, it's because you're from africa and have no past".
mircea_popescu: but he doesn't see this, so in he falls into pantsuit sink, "getting personal about profession is tremendously annoying" etc. no it's fucking not, jesus christ, jwz restated. have a better personality instead!
mircea_popescu: sn't, it's because you're from africa and have no past". ☟︎
esthlos: if you don't have any leads i'll mess around i suppose
asciilifeform: shinohai: you can't use gpg2 for this. nor stock gpg1
shinohai: ^ neat asciilifeform ... I'm a bit slower learning these bits (like debug flag 2 didn't work on gpg2 because mpi) but patience.
asciilifeform: if the good doktor writes in and asks, i'ma add a t.
mircea_popescu got the impression he named it deliberately for the acronymism (a lot more excusable in his case seeing how the uscongresstards hadn't yet driven that joke into the ground) and will sneak out to mix sugar in your fuel tank at night if you dare lop off the the
mircea_popescu: asciilifeform i don't remember that it can be. gotta to the hard way unbase64 etc
shinohai: Surely the autism can't be any higher than the tardstalk experiment.
mircea_popescu: can't imagine why, it must be just a feed like any other neh ?
BingoBoingo: Nah, they only don't ban insufficient world leaders
shinohai: I got my ban reversed, but simply couldn't bring myself to go back to that nonsense, figured I had rottede my mind enough. (Thanks alf)
shinohai: I have seen him on twitter before I left, don't know him exactly though.
mircea_popescu: http://btcbase.org/log/2018-01-06#1765939 << mircea_popescu does not see itself as any such thing, but that's entirely irrelevant. what mircea_popescu sees itself as or doesn't see itself as doesn't enter into it at any point, and you're misstating the problem. ☝︎
PeterL: and how do I know if I take random patch from you and stick it in my different patch tree that it will not break something? wouldn't I want to have the same world as you before adding your patch?
PeterL: and I don't see it as cut-and paste, you would just be changing the one line in the patch to merge it into your own flow?
PeterL: isn't that why we have a main-line version of software, so everybody is working on the same thing? does it make sense for everybody to be wroking on something slightly difference and expect my changes to fit your thing?
PeterL: couldn't having a standard of "touch readme file each patch" be a form of "don't do that"?
PeterL: you don't think it is broken that you were able to commit the "warcrime" so easily?
asciilifeform: PeterL: i dun particularly want anything ; i'm quite happy (aside from the can't-move-text-or-rename-files nonsense) with the way classical v works.
PeterL: so you want to touch comments in pertinent files after-the-fact, while I am suggesting touching a comment in a central file (README?) each time so that doesn't have to happen
a111: Logged on 2018-01-06 00:00 asciilifeform: i'ma summarize the v thing : if you have a proposed new v algo ; and it would turn my 1kB patches into 1MB, and my readable 3 lines into 100kLoc of ?#@%$*(@%% , and my trivial machine-diff-verifiable changes into 'why dontcha sit for 5 years doing eyeball-powered diff' -- it is NOT an improvement. and i won't touch it. sign it. sign anything made on it. etc
asciilifeform: rrything into 1file. this comes at a cost. apparently this particular electric fence must get pissed on empirically, for the cost to become obvious. let it be pissed on then, i haven't presently anything to add.
a111: Logged on 2018-01-06 06:28 mircea_popescu: as to the peculiar way in which http://btcbase.org/patches?patchset=eucrypt&search= renders the various arrows : it makes the implication that eg ch4 parents are ch3 "as well as ch1" for the coincidental reason that ch1 is included in ch4s parents both "indirectly" via c3 and "directly" in the lateral and unimportant sense that ch4 changes both files which were changed by ch3 and files that weren't changed since c1. this DOES
mircea_popescu: so no, at no fucking point does any patch have anything other than a single parent, which is properly speaking "the previous press", rather than "a random collection of files scattered about". like it or not, files don't have the sort of semantic power whereby a db.cpp "of the right hash" will always be useful when imported into some random project. files are not contextless ; neither because they aren't currently tooled to b
mircea_popescu: as to the peculiar way in which http://btcbase.org/patches?patchset=eucrypt&search= renders the various arrows : it makes the implication that eg ch4 parents are ch3 "as well as ch1" for the coincidental reason that ch1 is included in ch4s parents both "indirectly" via c3 and "directly" in the lateral and unimportant sense that ch4 changes both files which were changed by ch3 and files that weren't changed since c1. this DOES ☟︎
mircea_popescu: every single fucking line you produced in this attempt to double down on the "lalala i can't hear anything" idiocy is flaming, offensive bullshit.
a111: Logged on 2018-01-06 04:31 mircea_popescu: but yes, there is no other kind of code besides monolith ; i've had enough "bazaar" for three lifetimes of other people i don't particularly like ; and moreover code ambiguity is fucking nuts.
asciilifeform: http://btcbase.org/log/2018-01-06#1765888 << fughet, for the final time, 'bazaar', esr ain't here, and aint' gonna be here. and it is wrong to use the whip used for esr, on actual people. until you grasp this, your universe will not contain actual people. to unsheath the esr whip here is a fundamentally solipsistic act. ☝︎
asciilifeform: who wants to use -- go use. asciilifeform won't touch.
mircea_popescu: but yes, there is no other kind of code besides monolith ; i've had enough "bazaar" for three lifetimes of other people i don't particularly like ; and moreover code ambiguity is fucking nuts. ☟︎
a111: Logged on 2018-01-05 23:40 asciilifeform: think, if EVERY patch requires global regrind of all of world history, you ain't using v, may as well throw out all of the unnecessary equipment -- you're passing a monolithic turd around
mircea_popescu: http://btcbase.org/log/2018-01-05#1765461 << it wasn't supposed to, was it ? ☝︎
mircea_popescu: "this makes no fucking sense" needn't be either scary or worrisome -- it's the fundamental, unviersal state of mankind anyway.
a111: Logged on 2018-01-05 19:00 mircea_popescu: asciilifeform somehow you jump from "my printer is shit, doesn't work properly" to "either magic number or throw out printer"
mircea_popescu: this is very much the problem of thinking man, "i know what i like i just don't know what it is" ie http://btcbase.org/log/2018-01-05#1765170 ☝︎
mircea_popescu: for instance -- i did not observe then that "tab" makes 0 sense, entirely vt100.item to borrow your reference, and will not be maintained. CONTRARY to what i thought at the time, i don't like tabs, i like the thing tabs emulate, which is lisp autoindent
mircea_popescu: it is, isn't it.
mircea_popescu: when i ask for a deposit it won't fucking recur.
mircea_popescu: back at sanity ranch, ~only way to know it won't recur is the way trinque has it implemented
asciilifeform: they're simply 'i want a piece of shit that won't recur'
mircea_popescu: exactly a problem of "where the fuck is your engine" ie http://btcbase.org/log/2018-01-04#1763930 ie "your problem is that you aren't fucking thinking. AT ALL." ☝︎
mircea_popescu: absolute ban on english as an avenue to this much in the same way absolute ban to barking as an avenue to opera. i don't care if you're a dog and i don't care if barking comes naturally to you
a111: Logged on 2018-01-06 00:00 asciilifeform: i'ma summarize the v thing : if you have a proposed new v algo ; and it would turn my 1kB patches into 1MB, and my readable 3 lines into 100kLoc of ?#@%$*(@%% , and my trivial machine-diff-verifiable changes into 'why dontcha sit for 5 years doing eyeball-powered diff' -- it is NOT an improvement. and i won't touch it. sign it. sign anything made on it. etc
asciilifeform: understand, trinque , asciilifeform does not suffer from an irrational hatred of people who start with letter 't' , and thereby balk at $algo. asciilifeform genuinely does not see how it results in anything other than a http://btcbase.org/log/2018-01-06#1765616 horror show. ☝︎
asciilifeform: but they aren't meaningless. they signify 'you will have ~this~ db.cpp and ~this~ db.h and ...'
trinque: it's certainly easier to criticize that way, isn't it
trinque: ben_vulpes: don't cloud the politics with facts!
asciilifeform: i'ma summarize the v thing : if you have a proposed new v algo ; and it would turn my 1kB patches into 1MB, and my readable 3 lines into 100kLoc of ?#@%$*(@%% , and my trivial machine-diff-verifiable changes into 'why dontcha sit for 5 years doing eyeball-powered diff' -- it is NOT an improvement. and i won't touch it. sign it. sign anything made on it. etc ☟︎☟︎
asciilifeform: and at the risk of repeating , trinque can ~already~ do his style, in the existing v. whereas asciilifeform can't do worth shit in a trinque-style v.
trinque: hasn't yet been any reason someone benefits by having your edit to maxlocks but having done something batshit to say, a file db.cpp depends upon
asciilifeform: think, if EVERY patch requires global regrind of all of world history, you ain't using v, may as well throw out all of the unnecessary equipment -- you're passing a monolithic turd around ☟︎
asciilifeform: aite , if trinque gets it , i won't waste logspace
trinque: question there wasn't just moves. it was how to ever have two patches with same parent, that edited different files, end up same item.
asciilifeform: it doesn't solve the fundamental problem
shinohai: It's Alabama journalism, so don't expect too much ....
ben_vulpes: i know that it shouldn't, but i do like to actually test things
ben_vulpes: oh man i didn't even test against hex values
ben_vulpes: nah, dun expect such of me; i draft plans for field construction of catapaults i don't invent them
ben_vulpes: i haven't bitten off the patch yet, and might not get to it by the time you release ch6, this all takes me a lot longer than phf or lobbes
asciilifeform: or it won't go into ch6 (or anywhere)
ben_vulpes: the important thing is that it not be the same tempdir every time so that interrupted executions don't block the next execution
trinque: I'm sure it doesn't work. meant only to marketing-work
asciilifeform: which you naturally can't do from bios.
mircea_popescu: goes well with the "didn't even afford paralelconstruct". this is some seriously low effort "job".
asciilifeform: in fact, if we weren't planning to take gpg behind the shed and shoot it, i'd publish my keyring-abolition patch ( gpg then DEMANDS pubkey FILE on cmdline for any op that uses one. ditto privates. )
asciilifeform: i don't want to see it. ever. if i'm seeing it, vtron is broken !
mod6: and i don't think people want 1Mb of shit dumped to stdout
mod6: it sounds like my idea of "have something of a corpus to look at after failure" isn't as handy as simply just throwing it out.
asciilifeform: mod6: you can't make sure that the mains cord dun get pulled mid-press either
mod6: <+asciilifeform> mod6: afaik this dun actually happen on any known unix << this the rub tho. have to make sure that it actually /NEVER/ happens. i can't have people failing in anyway with this thing.
trinque: I don't think there's ever a case where , yeap
mod6: i shouldn't say a lot. from time to time, one of alf's previous key ones would creep into ones flow or whatever, and you may want to check for yourself weather it verifies or not. or what gnupg might have been up to while executing v.
mod6: and if it did fail, then perhaps one can go and look at what went on -- at the time, there were a lot of seals that didn't verify for instance.
asciilifeform: ( and given that i ain't his personal physician , i dun even care if he does the job while tripping , or while sober, so long as he does )
asciilifeform: i.e. what brings gabriel_laddel to #t ?
trinque: asciilifeform: I don't need extra reasons to hate the useless
trinque: who gives a shit. I made mine because it was trivial and I didn't want to hear about it anymore
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.
mod6: i know, i haven't had a chance to look yet.
mircea_popescu: this is the problem. you can't disagree with my theory and i have no practical solution for your pain.
asciilifeform: mircea_popescu: i can't at all disagree , re comments
mircea_popescu: asciilifeform somehow you jump from "my printer is shit, doesn't work properly" to "either magic number or throw out printer" ☟︎
asciilifeform: but 'throw out yer printer' won't fly.
asciilifeform: i won't disagree with abolishing'em when ~possible~ cleanly
mircea_popescu: there's a reason your father+grandfather haven't amounted to as much of a fart as a workable os.
ben_vulpes: asciilifeform: yeah i don't
mod6: i don't have a chance right this moment to do that, will look tho when i can
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
mod6: <+ben_vulpes> mod6: while you're in there can you get your vtron to cleanup its tmp gnupg directory when it catches a ctrl-c? << if you CTRL+C the thing, it really can't get rid of it. you're expected to clean this up on your own so the vtron doesn't remove something it wasn't suppoesd to.
asciilifeform: Stack(SP) , given as folx haven't been reading attentively, is top of stack.
lobbes: http://btcbase.org/log/2018-01-05#1764971 << porque no?? It isn't like it didn't mean that BEFORE you learned it. Plus, now you got extra layers: "I R SRS BSNS, ANAL!1!" ☝︎
phf: http://btcbase.org/log/2018-01-05#1764882 << hah, i read it and didn't notice that it was with fare. there's more fare interactions there of similar nature. ☝︎
mod6: There are better error messages, or averting a silent fail that will also help here. I haven't gotten that far on that part yet.
mod6: yeah, i actually did add a 'check_required' routine that is semi-related to this. for instance, when that error happened, it was because some guy didn't have `sha512sum'. so the check_required subroutine will now run first, and check to ensure that a list of system biniaries are available before anything happens. and if not, exits.