log☇︎
25800+ entries in 0.008s
asciilifeform: how wouldja describe for what
asciilifeform: tools for what ?
asciilifeform: to jump on ~your~ parachute, that you sewed.
asciilifeform: i'd hope that i dun have to explain that when you write a cryptosystem, you are in fact asking other people to do this.
asciilifeform: i.e. wouldja bet life of self, wives, pets, whole clan of yours, on there being no boojum in coq, z3, other claimed brain substitute of the day ?
asciilifeform: zx2c4: lemme ask you this -- those mecha-proofs of yours, how much do you actually believe in'em ?
asciilifeform: it was a misery. and 'sage' made it ~more~ of misery, if yer gonna commit 'machine proof' atrocities, has no biz doing in a non-homoiconic lang (i.e. any non lisp)
asciilifeform: sucked beyond my ability to describe.
asciilifeform: 'darpa' paid.
asciilifeform: zx2c4: you may find it interesting to learn that i once worked in a dour 'salt mine' where shat out 'correctness proof' all day. in 'sage.' ☟︎☟︎
asciilifeform: homeopaths at least only bamboozle the irredeemably stupid
asciilifeform: as it is i have less nausea for even honeopaths than for mecha-proof folks
asciilifeform: and i'm to take it seriously after that ? pray tell why ?
asciilifeform: i have not read src of coq, to do so would take 20yr ( and i dun mean 'skim', but to find total proof of correctness of whole shebang and load into MY head )
asciilifeform: zx2c4: lemme ask, on what authority am i to accept the correctness of a proof generated via e.g. coq ?
asciilifeform: intellectual bankruptcy.
asciilifeform: haskellism is like dope for intellectually-bent folx. it is addictive but ultimately ruin.
asciilifeform: zx2c4: whole reason i bother with this thread is to explain why no, i would ~not~ like to suck the coq, if you will
asciilifeform: or that ~ nuffing in asciilifeform's machine room postdates '09
asciilifeform: or that FUCKGOATS rng is built to speak rs232 at 115200 baud and always will be
asciilifeform: ( wait till he learns that asciilifeform has a fleet of e.g. dos boxes. )
asciilifeform: deadly serious.
asciilifeform turns 35 next wk
asciilifeform: depends how you consider
asciilifeform: but is immaterial, next will ask what kinda chalks.
asciilifeform: ( on some occasion, also macsyma )
asciilifeform: 'derive'
asciilifeform: i sometimes even use computer algebratrons, in exploratory work. but would never consider presenting output straight from one as 'here, correct'
asciilifeform: but they are devices for eventually rearranging contents of your head, permanently, rather than substitutes for head,
asciilifeform: zx2c4: i like paper. and even chalk.
asciilifeform: grasp obvious in its totality, as in there is literally NO hesitation to strap the thing on and 'if mistake -- any mistake -- i hit cement at terminal velocity'
asciilifeform: so long as in the end it clicks in your crankcase and is as obvious as that and gate.
asciilifeform: lemmas ok, paper ok
asciilifeform: with me so far ?
asciilifeform: let's take from other end of digestive tract. consider 1 AND gate. idealized, no metastability, no breakdown voltages, literally 'ands' two logical values. ( can have physically limited to % of c speed, if you like, but this is uninportant )
asciilifeform: the attribute which permits this approach, vs haskellism and other idolatrous rituals to mechanical molloch, is called 'fits in head'.
asciilifeform: the statement is quite serious, i and some yet-unknown number of other people will literally bet arse on our grasp of ffa correctness.
asciilifeform: ffa. see esp the passage re parachute.
asciilifeform: fortunately there is a convenient demo
asciilifeform: ^ see also.
asciilifeform: !#s heaviside
asciilifeform: gotta actually exist ( and 'genius' btw is the fella who makes the 'fit in 1 head' fit in 9000. )
asciilifeform: not enuff to 'posit'
asciilifeform: this is a political declaration, not an astronomical observation, zx2c4
asciilifeform: zx2c4: theorem that dun fit in any 1 skullcase, aint proven.
asciilifeform: not fits in head ? not proven. ( i did not say ~whose~ head, but imho safe to suppose that whole f# microshitiana garbage pail fits in no head )
asciilifeform: then they aint proven, basta.
asciilifeform: if you need a 'proof system' to prove $assertion, you have NOT proven it. not to me. ☟︎
asciilifeform: zx2c4: try to think about what i actually said tho
asciilifeform: have seen
asciilifeform: proof is proof when it fits in head, now just as in euclid's time.
asciilifeform: wtf is the point of 'here's a proof but you need this here 100MB of gnarl to ~run~ it and of course you will trust output, or are you a terrorist'
asciilifeform: and, in parallel, to be an organized campaign of sabotage against ~concept~ of actual correctness in programs.
asciilifeform: zx2c4: point being, i don't practice haskellism. and nit from being illiterate yokel who has nfi how. it so happens that i know how. but consider the whole approach to be braindamaged .
asciilifeform: http://btcbase.org/log/2018-05-04#1809389 << prev visit ☝︎
asciilifeform: zx2c4: weren't you here last yr for a 'the technical cannot be separated from the political' and 'if program+all accessories doesn't Fit In Head, it is garbage, not proof' thread ?
asciilifeform: the what?
asciilifeform: in all seriousness, i don't even presently know of a more leprous pile of shit, either on pedigree or technical pov.
asciilifeform: http://btcbase.org/log/2017-03-30#1634699 << summary ☝︎
asciilifeform: ^
asciilifeform: !#s rust
asciilifeform: zx2c4: didnt mircea_popescu send you a coin ?
asciilifeform: zx2c4: long time no see. what brings ya back ?
asciilifeform: !#s zx2c4
asciilifeform: brb
asciilifeform: ( than wx were )
asciilifeform: 100x fatter turd mass
asciilifeform: mircea_popescu: wx liquishit , qt, jettisoned loong ago. but bdb, openssl , boost, remained
asciilifeform: ( observe -- sans agression, the moar reliable is your hosting, the ~more~ certain your noad is to get perma-wedged, as it'll never reboot and never satisfy shitoshi's 'catch up only on cold boot' idjit condition.. ) ☟︎
asciilifeform can't even count nao how many time had convo, 'hulp! my noad is hanging' 'didja aggression' 'no...' '...'
asciilifeform: srsly, whoever's poor neglected box this is -- fucking put in 'aggression' or pull the plug, thing is eating mains current to no useful end
asciilifeform: !#s 69.197.146.42
asciilifeform: unrelatedly, to whom does trb noad 69.197.146.42 belong ?? it's been wedged for year+
asciilifeform bbl,teatime
asciilifeform: right. ( and as presently stands, i've abolished all but 1 of the algos where this actually takes place )
asciilifeform: on 2nd pass of log, noticed that i did not answr http://btcbase.org/log/2018-11-29#1876084 : answr is, it is for shifting ~into~ a FZ . ( if this wasn't clear from thread ) ftr. ☝︎
asciilifeform: anyffing that dun make immediate sense in ~that~ light oughta be either changed or commented.
asciilifeform: diana_coman: this is a+++ good, it is exactly how it is meant to be read
asciilifeform: my current aim is that in ch22 ( see also http://www.loper-os.org/?p=2735 ) any subcomponents not used, are to be cut; and any that have strictly 1 invocation, are to be made sub-functions and remain visible solely in the scope where used.
asciilifeform: orig was writing from pov of 'most general possible set of subcomponents' , but this is not necessarily what is wanted in the end product, esp. from loc-cut pov.
asciilifeform: at 1 time, was used in the constant entry ( nibble inserter ) routine, then the latter was replaced with rewritten http://www.loper-os.org/pub/ffa/hypertext/ch13/fz_io__adb.htm#29_14 , nao sole remaining use is in the knuth divider.
asciilifeform: 'best rake is no rake'
asciilifeform: diana_coman: i'ma also note, _O_I is used strictly in fz_mod : http://www.loper-os.org/pub/ffa/hypertext/ch13/fz_divis__adb.htm#83_14 ; prolly oughta be inlined ~there~ and abolished as a global (even internally) function.
asciilifeform: (this is, for most part, already what cmdline does. aside from 'maxsteps' not having yet been introduced Officially, cuz no loops yet)
asciilifeform: i.e. one will call, roughly, P(pcodestring, ffawidth, ffaheight, maxsteps) and get output.
asciilifeform: incidentally even the currently given 'external api' is eventually to be 'internalized', in the sense that user input is expected to be in P-code (presently named as 'ffacalc') and output ditto
asciilifeform: and in principle i'm not averse to adding detail to comments. ( this is exactly the reason why comments exist -- show what is not necessarily evident from the coad )
asciilifeform: right
asciilifeform: ( the only guarantee i can offer in good conscience is that nuffin can be broken by operating the ~external~ controls -- but even there user is required to see whether his cpu has barrel shifter (see ch13 discussion) , constant-time mul ( see ch9 discussion ) )
asciilifeform: i'ma add commentary/warnings when diana_coman et al point out good additional places where; but no one should live with expectation that ~all~ possible ways to break ffa by monkeying with internals, will be listed
asciilifeform: but the same guarantee cannot be given for erry internal component, not without geological runtime.
asciilifeform: idea being , exported routines ( current set is shown in http://www.loper-os.org/pub/ffa/hypertext/ch13/ffa__ads.htm ) are to be 'safe on all electrically possible inputs' , with the exception of div0 (user is commanded to test for div0, as example in http://www.loper-os.org/pub/ffa/hypertext/ch13/ffa_calc__adb.htm#172_17 )
asciilifeform: and this is prolly not the only instance of the item. ( i discussed it briefly in ch11 , in the section where preconditions -- ended up moving many preconditions to the exported wrappers, they slow things down quite substantially when present on inner-looped invocations, as they prevent (for obv reason) inliner )
asciilifeform: diana_coman: i'ma absolutely add it to comment and discuss in ch14 mail bag.
asciilifeform: this is one of the reasons why.
asciilifeform: observe that the operators of fz_shifts are not exported in ffa.ads ( ch11 unified api ) , they are strictly for internal use in the lib.
asciilifeform: it will produce garbage, yes. i considered to make OF_in a limited type, but it would slow down the place where the item is actually used, substantially ( ada does not offer a fast bit-count-on-word operation )
asciilifeform: you mean, what if one were to feed it one when cascading ?
asciilifeform: diana_coman: how would a shift by 2 provide overflow of 8 ?
asciilifeform: diana_coman: plox to link to line ?