log☇︎
134300+ entries in 0.084s
asciilifeform: how is that speciousargument
mircea_popescu: you use machinery to turn data to comfortable representation ; the "human readable" is not about "being able to stuff my dick in power socket".
mircea_popescu: asciilifeform this is a specious argument ; "o noes, little em impulses on a platter are nor readable with my puny fingers"
asciilifeform: much as i like sexpr, a sexpr dump of a vector drawing is not humanreadable either. at least not with my puny brain, i have nfi, perhaps mircea_popescu can render these in his head as he reads'em ?
mircea_popescu: "svg". the thing that svg should have been.
asciilifeform: i'm still waiting to hear how mircea_popescu would represent e.g. the fg schematic, in ideal vtron.
mircea_popescu: asciilifeform if people thought in asts it'd be computers programming them.
asciilifeform: there ain't actually any orc glyphs in my patches tho
mircea_popescu: and the whole arguments with alphabets and alf's perennial "but i r creative speshul snowflake, must has hyeroglyphs"
asciilifeform: whether it 'is' in fact ast, or merely representably as one with 0 loss, is the open q afaik
mircea_popescu: and "asciiart" is imo the wrong direction to take at the "asciiart or literate code" fork in the road.
phf: the ast direction moves away from patches as literature (which is i think what mp is saying from a different direction?)
asciilifeform: right. but the 'source' in yer head is, really , an ast, whether you end up hitting space 1ce or 3ce when you end up entering the text. and likewise when i read it, it gets reparsed into ast.
mircea_popescu: but what we're diffingh and patching are properly speaking our own notes, not the asts.
a111: Logged on 2017-12-18 02:05 mircea_popescu recalls somewhat fondly old days of "put the model in and wait a few hours for to find out how you fucked it up this time"
mircea_popescu: asciilifeform the problem is that no, not really. everyone is eating the "cvasi-hulang description of a meta-ast then watching in trepidation what ast comes of it". as per that http://btcbase.org/log/2017-12-18#1753058 ☝︎
asciilifeform: ultimately everyone is really eating the ast.
asciilifeform: that's what linear array text is a cheap, impoverished hack approximation to.
asciilifeform: the closest we can prolly ask for to 'hash meaning' is sexpr/ast.
mircea_popescu: trinque exactly my tho9ughts. "i don't want to go there. yet."
trinque: the whitespace thing though is a fine cut of it, since the next step incurs orders of magnitude more complexity (parser per lang)
mircea_popescu: asciilifeform it's unfortunate that hashes can't hash meaning, but then again we're stuck with babbage looking over one shoulder and turing over the other.
asciilifeform: we actually had the ast-diff thread, re phf's lisp diff lament. ☟︎
trinque: heads towards ast-diff, and people have their presentation layer do whatever with the ast while coding.
phf: " I use space as a terminator and words execute immediately, there is no CR to mark the end of the line. There are no CRs, just space delimiters. I currently have BS and Delete. I would like to keep only two special keys, BS and a key to exit. I think I would prefer BS over Delete."
asciilifeform: a whitespace-agnostic diff would be a not-useless thing. problem is that hashes are not whitespace-agnostic, nor could ever safely be.
mircea_popescu: anyway, this is the important, v-powered realisation here : there can NOT BE such a thing as bit-ambiguity in a source. if "this bit being either set or null has no effect" you have a problem, which must be addressed. because it sure as fuck isn't acceptabru to read diffs of style in a patch. patches are for substantive change.
asciilifeform: aa so teletype.
phf: asciilifeform: i've had a more detailed quote on the dead machine, but the less detailed equivalent is “I use my own 0-Z character set. It is a six bit character set. It only has upper case and there is no distinction between the letter "O" and zero.”
asciilifeform: it isn't untreated, it gets skipped. ( 'p' prototype in 'strict' mode will also stop and eggog if encounters a non-7bitclean char. which one can connect to a stick, to beat author of input )
mircea_popescu: asciilifeform machine is to take over stick from my hands in all domains.
mircea_popescu: because you CAN NOT have such a thing as untreated item in code.
mircea_popescu: just as soon as something "is ignored by the compiler", that something now has to be treated somewhere else.
asciilifeform: you solve the problem by beating people with a stick, who emit the shit style.
mircea_popescu: that's the thing : the moment you have unconnected expression, which is to say \t = " " you suddenly have the problem of style.
mircea_popescu: "no other char than tab up until the first alphanum in each line" is a fine rule ; and if someone discovers that he can't press his homebrew let someone fix his homebrew.
mircea_popescu: exactly re <asciilifeform> ( who recalls the mircea_popescu tabs-spaces thread... )
mircea_popescu: i am NOT looking at difflists saying "and then special snowflake added a space and took out a tab"
mircea_popescu: something IS gained thereby.
asciilifeform: mircea_popescu: i like breaking things when something is gained thereby.
mircea_popescu: wait i thought you didn't like it.
phf: asciilifeform: chuck moore did that though..
mircea_popescu: code is not natural language. code is a highly structured, deliberately limited-expressive form of language. what is said re http://trilema.com/2010/hai-sa-studiem-gramatica-impreuna/#selection-99.0-99.995 goes triple for code
asciilifeform: i'm almost surprised that mircea_popescu hasn't yet thought of , e.g., anathemizing ascii in favour of own, arbitrary arrangement of alphabet, strictly for incompatibility's sake; or to proclaim the 17-bit byte...
asciilifeform: adding arbitrary talmudiana is what microshit is made of.
mircea_popescu: the "backward compatibility" argument is no argument but a red herring. i will not break shit to match microsoft's sad history.
mircea_popescu: also -- if v breaks fortran then FORTRAN fixes itself.
mircea_popescu: for testing etc, fix i expect will be used. for publishing, i expect not.
mircea_popescu: asciilifeform option is there. either fail or fix.
mircea_popescu: which is something that was blunderingly and un-intelligently a red thread throughout coding ever since linux opened its eyes.
asciilifeform: i guarantee that the 'autofix' will break something, somewhere, at some point, in a difficult-to-detect way.
mircea_popescu: exactly what the rules are is an open question, but basically the idea is to separate style from content in code.
mircea_popescu: the way this'd work would be as a list of rules ("no two consecutive spaces" or whatever) which the sources are checked against BEFORE diffing. should the check fail the options are either to propagate the fail ("file x not in format" error) or else to autofix (which'd work via sed).
asciilifeform: mircea_popescu: plz expand then ?
a111: Logged on 2017-12-19 17:35 trinque: hm, dunno whether I want to execute someone's script during a press.
mircea_popescu: http://btcbase.org/log/2017-12-19#1754358 << entirely not what's contemplated here ; asciilifeform spurious overloading of the concept unwelcome. ☝︎
asciilifeform: sanity will involve a much greater degree of kitchen-toilet-separation than seen today.
asciilifeform: ( the long-time reader will observe that this contravenes http://www.loper-os.org/?p=231 . tough cookies, don't do crypto on box with transparent copying. )
asciilifeform: ( and naturally 0 swapolade or any other 'transparent' copying of anything at all behind the operator's back, in the whole machine, goes without saying. )
a111: Logged on 2017-05-16 01:53 asciilifeform: now you store bit as ~phase~ of the square wave, rather than absolute steady state of the flipflop.
mircea_popescu: which yes, kock wouldn't be koch if he didn't live to try and befoul the tools of salvation through association with his turpitudes.
mircea_popescu: but the concept itself is sound.
mircea_popescu: so in this sense i agree "secure memory" on current iron is not worth bothering with.
mircea_popescu: ofcoruse such a thing can not exist until we actually make tmsr-computer without dma
asciilifeform: trinque: sorta why i didn't particularly itch to go there
trinque: or at least, scripting would have to be severely limited, lest the thing become vthereum
trinque: hm, dunno whether I want to execute someone's script during a press. ☟︎
asciilifeform: ( who recalls the mircea_popescu tabs-spaces thread... )
asciilifeform: incl. mv, cp, tr/sed.
a111: Logged on 2017-12-19 16:57 mircea_popescu: phf the correct approach to this is pre-diff filtering masks.
asciilifeform: http://btcbase.org/log/2017-12-19#1754311 << this is how asciilifeform originally thought to make the file-moves thing, with the 'manifest', i.e. list of commands that get executed on the dataset pre-diff ☝︎
a111: Logged on 2017-12-19 17:13 mircea_popescu: and yes, the original holder threads were never meaningfully revisited. this is a 10yo suture wound with the first silks still attached.
trinque: can't waste all the security anointing oil on one proggy. gotta save some for the rest of god's children!
asciilifeform: at one point asciilifeform planned to cut out the allocator from mpi entirely, but ditched whole thing before ever getting there.
diana_coman: asciilifeform, it's fine to say no secure memory,sure; it's not fine to pretend it is used but then "use" it like in the example
asciilifeform: ftr i dun plan to include 'secure memory'ism in ffa.
diana_coman: mircea_popescu, myeah, I suspect it's sloppiness, "but it's same thing"
asciilifeform: the 'secure memory' thing is entirely red herring imho. all it means is that it gets marked unswappable. but i dun have swap on any of my boxes, period.
a111: Logged on 2016-07-08 14:37 mircea_popescu: fucking "take moar oestrogen" confucius & "wanna hear our inept teenage boyish oneupmanships" zeo-dan derps.
mircea_popescu: cheap "cleverness" of the male virginarium aka monastery ; in same vein see also http://btcbase.org/log/2016-07-08#1499583 ☝︎☟︎
diana_coman: and in more recent lol-with-gpg: the primegen function in gpg allocates secure memory for candidate prime when generating for rsa BUT then it goes on and calls is_prime on that "n" and is_prime calculates and stores n-1 in ...insecure memory ☟︎
mircea_popescu: in that it bakes metasyntaxis into the code.
a111: Logged on 2015-05-20 00:29 mod6: take a look at this: http://dpaste.com/0SQPBKC.txt Is there any reason when allocating the space for p & q to do Eulers totient they would initialize the space with 'p' and 'p', instead of 'p' & 'q'?
diana_coman: in "only 2 years later" but since I did not find otherwise in the logs an answer to mod6's question at http://btcbase.org/log/2015-05-20#1139680 : that is simply the number of limbs, so a matter of size; since p and q are same size, it is fine there although arguably not helping the reader ☝︎
BingoBoingo: Metaphores can trasmit tastes!
mircea_popescu: because hey, "core developers" too busy eating my asshole.
BingoBoingo: shinohai: The critters have numerous avenues for developing resistance to contact insecticides, so applying permethrins is typically an arms race. Hence leaning towards the imaclopramid solution.
mircea_popescu: and yes, the original holder threads were never meaningfully revisited. this is a 10yo suture wound with the first silks still attached. ☟︎
trinque: and if I understand this "trickle" thing correctly, wtf, that's coming out. what privacy? blast my txn to everyone you know.
shinohai: That sucks, ou'll have to grow a fuckton of chrysanthemums and extract our own.
trinque: yeah, I'm cracking the thing open for maximum external control.
trinque: mod6: this will probably end up being a separate branch. my needs with deedbot are diverging from "preserve grandfather's pistol".
shinohai: Are pyrethrins legal there?
BingoBoingo: <shinohai> Except the pests are actual insects << Aha, persistent bugs, but yes. Can not fault them for following travellers.
trinque awakes to see a trb node with wallet excised, synced to 200k
mircea_popescu: (editor, as in, the human person, not as in the "editor" ie ide)
mircea_popescu: when i diff i want to see what you changed, not what your editor changed.
mircea_popescu: yes. but it is a conceptual failure on the part of diff that it presents these.
a111: Logged on 2017-12-17 03:52 mircea_popescu does his usual s%\n\n%\r\r% s%\n% % s%\r\r%\n\n% while muttering underbreath about the idiocy of fucktards who STILL DON'T UNDERTAND NEWLINE STANDS FOR NEW PARAGRAPH!!11
mircea_popescu: phf the correct approach to this is pre-diff filtering masks. ☟︎