tmsr - Search: gnarl

asciilifeform: lobbes: if you abstract past the hieroglyphs-- is easier to eat than any euro lang. no declensions, no conjugation , very little of what euro folx normally think of as grammar gnarl.

asciilifeform: the beauty of synthetic 'iron' is that you can actually use just about any kernel, because there is no driver gnarl, you're already baking the drivers with own hands

phf: asciilifeform: right, snabb doesn't have some of our restrictions, i.e. they accept all kinds of modern gnarl in exchange for the ability to send raw packets. i'm not sure their approach even works on old cards

asciilifeform: spyked: not only is the implementation what it is, but tcp per se is massive pile o'shit, where it aint even possible to implement it w/out 9000 tonnes of state machine gnarl

mircea_popescu: yes, but consider : as a counterpart of the "gnalr contest", which imo is not that bad of an idea even if it flows necessarily from the ~nature~ of the substrate, "only intellectually challenging thing to do in c++ is gnarl, much like only thing to do with mud is mess", one could also resurrect ye olde game of life (remember the mike_c project ?). construct say the tape that has the most interesting downstream (by some ~abstr

mircea_popescu: asciilifeform imo it's a decent exploration of ye olde negative space. "how would one write gnarl in peh, and how would one automate such, and so on"

mircea_popescu: and willy nilly we run into the gnarl of idiocy that is posix. wtf is a "stderr". ☝︎

asciilifeform: the tard arch people passed the 'register killing' ball to compiler, as result bloating ~all~ compiler with massive gnarl, ~just for reg killing logic~

mircea_popescu: coincidentally : is anyone from the adacore/gnat/gnarl/whatever days still breathing even ? or 100% bolix situation, "documents at warehouse, i am machinist in charge" ?

asciilifeform: this can be worked around, but would add gnarl, and i won't touch it unless someone gives a compelling argument re why oughta build on a -83.

a111: Logged on 2019-01-09 15:36 asciilifeform: last night i re-read diana_coman's piece on m-r , it is interesting just how much sweat diana_coman had to put in simply on account of koch gnarl

asciilifeform: last night i re-read diana_coman's piece on m-r , it is interesting just how much sweat diana_coman had to put in simply on account of koch gnarl ☟︎

asciilifeform: also suffers from practical gnarl -- say the session gets thrown. how many times is the bot to retry upload.

asciilifeform: phf: funnily enuff, i did the gnarl of the bus already, during (aborted) proj for dks where he asked 'make me a replacement crapple mem expander board for nubus'

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: funnily enuff, an almost ~exact opposite~ of asciilifeform's experience in digging up ada ( reputation for gnarl, turns out actually simple & clean 'when used as prescribed' ) , risc-v - reputation for 'simple and clean', turns out ball o' hair

asciilifeform: speaking of heathen gnarl, took another look coupla wks ago at 'risc-v' ( e.g. instr set https://archive.is/TfPrq ) and pretty depressing. yes it's the simplest cpu currently targeted by gcc , and somebody even sells iron nao, but still a mess.

asciilifeform: ( i've seen various heathen crapola that takes pdf and makes www, but all seems to use ocean of js and scarcely improvement over orig gnarl imho )

asciilifeform: it is possible that there's some format gnarl that i haven't accounted for , tho, i haven't tried erry elephantine key on it ( should really test by walking phuctor db )

mircea_popescu: i'm naively assuming it wouldn't, but in fairness haven't actually looked into the gnarl.

mircea_popescu: notice ~why~ it is random derp uses [ie, acts as if has loaded in head] pile of gnarl like say excel, or "telegram" or "kubinetes" or w/e : FOR LOVE OF BROTHER. "we all do it". but it sucks ? "yes well."

asciilifeform: mircea_popescu: iirc we had a thread re this ; the gnarl is roughly similar to xilinx reversing ( they switch chip revisions erry quarter or so, by the time a card is ~acceptably reversed , it is long out of print )

asciilifeform: i took a shot at building one back in 2016, but ran into a buncha gnarl, which ave1 at this point seems to have mostly resolved

mircea_popescu: people who expect to run it atop musl as opposed to atop gnarl, that's very much who.

asciilifeform: the gnarl begins with the fact that all of these modes, were created by different folx, with no coordination

asciilifeform: ( funnily enuff, the pain of 'modern' html, exactly mirrors the pain of vt 'enhanced' with 'terminal control' gnarl, 35 yrs ago )

mircea_popescu: l approach for one hobbist in finland to lift into his own head the gnarl of 386.

mircea_popescu: i suppose if you actually make the http://btcbase.org/log/2018-02-19#1784956 item then that'd prolly want its own #pizarro list ; but also by now it's such a complex piece of gnarl might even want to separate a rss-bot out of deedbot ☝︎

mircea_popescu: that's the major challenge : can the argument be constructed to see what is actually wrong with that piece of gnarl ?

asciilifeform: http server ? fwiw adacore distributes one. ( i dun like it, for same reason as apache -- it's a megatonne of gnarl . but, it does in fact work, and benefits from the language guarantees etc )

mircea_popescu: would look like all gnarl, but anyway.

mircea_popescu: asciilifeform you seriously \ out oo-cpp gnarl to 80 ?

mircea_popescu: ye olde sunfunction clocks, rite ? some of the best piles of fine gnarl the world has ever seen

mircea_popescu: and in other "asian people should just be holocausted" news : piece of shit router, gets set up to work on static ip, spews out the helpful error message of "the value can't be equal". verbatim. and the source of it is a pile of inclusion gnarl so you can't even trivially debug the nonsense THAT way.

mircea_popescu: just tee it to file / use screen and copy screen log as a standard practice when fighting build gnarl

mircea_popescu: the compiler for arbitrary this arch would be one helluva piece of gnarl.

asciilifeform: phf: you're quite right that it isn't. thing is an astonishing pile of gnarl. but all of the necessary info, is ~inside~ it, just like 'bitcoin' lives inside the rubbish of trb

mircea_popescu: i dunno, it does some exporting gnarl. diana_coman published a recipe, i can dig it up if you wish

mircea_popescu: if only. the pile of gnarl is unfuckingtraceable.

mircea_popescu: it's some sort of javascript gnarl ; failed to work on first pass and i'm not debugging it. whatever, two girls next door doing whatever.

mircea_popescu: asciilifeform yeah. i just meant the vidcard gnarl could maybe be excised in a politically defensible manner. historically it was ~60 to 70% of all the mess.

asciilifeform: it is not actually hard to massively improve on cadr, much of its gnarl was that it had to be made of 74xxx and of weird amd ALUs available at the time

asciilifeform: also ianal but there is probably more gnarl to it, otherwise usg would have to charge, e.g., dope peddler, with trespassing on usg property by occupying his house the day after the dope peddlin' , etc

asciilifeform: and much of the gnarl in this thread stems from attempts to somehow work around this fact

asciilifeform: now, a system with built-in notion of bignums (variable-length integers), e.g., lispm, does not suffer from any of this gnarl.

mircea_popescu: anyway, lots of maxsigop gnarl in there, not really worth the mention.

mircea_popescu: this, i'll grant, is an insane piece of gnarl with three joins in it. for prototyping not really used in code.

asciilifeform: punkman: get the 'rationale' book. every piece of 'gnarl' is justified, and the justification reads like your local fire code - every line is likely there because of a corpse

mircea_popescu: eh fuck em, you tell me someone's going to bother select that gnarl and paste it in browswe window ?