131000+ entries in 0.072s
mircea_popescu: but if you feel like
the reading, about ~any history of
the benedictine order in
the early history of europe (say 10th and 11th centuries) should prove an informative read.
phf: one is an accumulation of knowledge on
the subject of history in your head,
the other one is a written book of
that
title,
that one, if one were so inclined, could
track down and read :)
phf: oh so it's
the history of cluny, rather
than "The History of Cluny"
mircea_popescu: (gaul was, in
the estimation of
the romans
themselves,
the better part of
the empire, which is why most moved
there)
mircea_popescu: phf
the barbaric lands were slowly recivilised after
the fall of
the roman empire.
the effort centered around
this fortified monastery in gaul, and its satellites
phf: mircea_popescu: i'm not, what is
that?
mircea_popescu: "what if
the northern part of new world was actually important and like, events happened here and shit ?~!?!?"
mircea_popescu: btw, you are aware
the canticle is just history-of-cluny with
the serials (and most of
the good stuff) shaved off ?
pehbot: asciilifeform:
take precedence over []
phf: asciilifeform: yes, but it's going
to be shorter for mp
phf: the nick is going
to make a difference, it's 250 characters by
the way
mircea_popescu: the paste idea is pretty good, in
that it
takes
the (unavoidable, btw) line issue away entirely.
ben_vulpes: what i did for candi was
to link a paste
mircea_popescu: there;s
this whole pile of 2nd world "Cinema" made by 30second ad people.
a111: Logged on 2017-05-16 01:36 asciilifeform: in other near-term lulz, a 'pbot' is in
the worx, so
that folx can play with various input->output pairs in-chan
phf: asciilifeform: hey when you adjust
the filters, can you make sure manual spacing still works?
mircea_popescu: nice. will make a great
tool i expect, can reference bot in examples etc.
mircea_popescu: and is it getting updated in step with
the ffa publishings ?
pehbot: asciilifeform:
this prints some
text
pehbot: asciilifeform:
this prints (but
this is a comment) some
text
phf: yeah,
that makes sense
mircea_popescu: asciilifeform !A help would be nice once you get around
to it.
pehbot: asciilifeform: some actual
text
phf: mircea_popescu: well, i
thought he's got some minimalist
tendencies, like left shift is done with a bunch of 0's and right shift is done with a combination of
twig and rock
phf: mircea_popescu: is
there any reason
there's no right shift in p? or
there's some way
to do it with what's
there?
mircea_popescu: sure, i'll be happy
to look up what
the
thing should be in preference of your doing it. lessee.
mircea_popescu: asciilifeform other
than
the wrong control sequence / your utter ignoring of
that whole mechanism,
the bot is compliant, spits out one line per command, can sit forever.
a111: Logged on 2017-12-29 01:44 esthlos: fwiw I read McIlroy's paper and would be willing
to implement it _transparently_, if
there's interest
mod6: i kinda like
this
thing, and while your loper posts are fresh, i'd like it hang for a bit.
phf: though come
to
think of it, in colorforth it'll make
things more expensive (since now each digit basically costs a header-and-a-word's-worth)
mircea_popescu is willing
to bet chuck moore is
too dumb
to figure
this out.
phf: i feel like you chould email it
to chuck moore, he'll get a kick out of it "saves 25 bits on my greenarray cluster!"
ben_vulpes: freenode is
the kludge; im not going
to sink
time into making *tronic bot
that doesn't do auth itself because freenode doesn't like your host.
phf: well, . puts a zero and
the 1-9A-F mutates
the
top, so you don't have
to have state in
the parser
ben_vulpes: asciilifeform: i am not going
to
take responsibility for your not reading
the connection routines. it's plain as day
the
thing expects magic strings.
phf: asciilifeform: i like
the .
trick by
the way, is
there prior art
to it?
a111: Logged on 2017-12-29 00:54 asciilifeform: possibly
this is it.
phf: thing expects a complicated challenge response state machine
to happen
phf: asciilifeform:
that would be
the case with
trinque's bot
too
phf: but
then i can also understand
the whole "back in my day" sentiment. common lisp certainly lets you write ~very sloppy~ code and get away with it :>
☟︎ phf: i had
that experience when i
tried implementing an older spec of gossipd. i wrote it in C, actually CWEB, but i wasn't doing literate programming right, and after a while
the whole
thing became overwhelming.
esthlos: even with small C projects I start
to panic when I realise I don't know how it works anymore
☟︎ esthlos: certainly I can't write elegant C
tho
esthlos: elegant C exists, but
the limits of
the language
the complexity it can handle without exploding into incomprehensibility.
☟︎ phf: i mean, if you read norvig's python snippets you can clearly see
they are written by a very experienced lispers. you literally never see python like
that in
the wild, but yet
there it is.
☟︎ phf: but i actually really want
to learn
to spit out elegant C like knuth, djb or rob pike
esthlos: it seems specifically designed
to reduce
the intelligence of
the programmer
to what a manager can understand
☟︎ phf: that would be a very gruesome science fiction narrative, if
that was actually
the case. a kind of strugatsky's roadside picnic :>
☟︎ phf: please do, it would be useful as a reference, but also for me specifically: btcbase.org/patch is written in common lisp, but it can only eat vpatches, not spit
them out, so a mcilroy would be a solid addition
esthlos: phf: alright, I will have
to read up. my practice v implementation will be in CL, and I was
thinking of implementing mcilroy for educational purposes. if such an implementation sounds useful, let me know
phf: this follows ascii's pattern of
trying
to bend existing
tools
to our needs, before we know enough
to do a greenfield rewrite.
there's a lot of ideas floating around what v is supposed
to do. a clean rewrite of mcilroy could serve as a basis for further work, but you should perhaps follow discussion in
the logs on
the subject
to get
the full scope of
the problem
phf: what you have on
top of original paper is unified diff format and
the handling of multiple files in a single patch. (that's where you run into
the bulk of extra code;
things like sorting directory is simply unpleasant
to do in C)
phf: what i'm
trying
to do is not so much a rewrite, as first an ascii style cut of relevant bits,
to preserve backwards compatability with current patches, and
then augmentation
to support various operations
that were discussed in logs,
that are more about file management
than
they are about diffing
phf: well,
the context of what i'm
trying
to do is in
the logs. specifically mcilroy diffing implementation is not necessarily
the problem (relevant bits of gnudiff are reducable
to maybe 500-1000 loc)