226900+ entries in 0.138s
ben_vulpes: asciilifeform: no, it's not phf's, it's magit and i
think ediff
adlai: asciilifeform: i refuse
to get into "clhs doesn't actually say you're not allowed
to give it an atom"
territory
a111: Logged on 2017-01-04 08:25 ben_vulpes:
http://imgur.com/a/KuPJv << some kind of voodoo magic in
there knows i moved
that format string around
☟︎ adlai: asciilifeform: in other wtf, isn't ., isomorphic
to ,@!?
adlai: sure, you can write
the whole
thing in forth (or lambda calc, or categories, or...), but as
the agent said
to
the provocateur - 'good luck'
adlai: students can build multiple impls as hw, but anybody using a forkable client is
taking a risk
adlai: but it's correct as a version number, because consensus systems fail correctly
together, and "history is written by
the victors"
mircea_popescu: hm i could have sworn it was used before, "ideal bitcoin" ie
the
tmsr offering in
the summer of forks. bitcoin v2.0, whatever
adlai: is
that a version 'number'?
mircea_popescu: if we make
the
trb-i correct it should work like vtrons, multiple language implementations
mircea_popescu: but for eg
trb work, +++ style is quite at home. it is c after all
ben_vulpes: asciilifeform: i had a complaint about
this a while back, reindenting for multiple-value-bind and destructuring-bind and friends
a111: Logged on 2017-01-05 00:43 asciilifeform: incidentally you will blow up on
the +++ mine if you
try and diff a vdiff.
mircea_popescu: and how am i going
to apply patches ?
there's no such
thing as signature-equivalence.
mircea_popescu: i didn't bring up
the fucking apocalypse
to fix some
tabs.
mircea_popescu: i do not wish
to live in a world where people can make patches consisting of 512kb lines of a
☟︎ mircea_popescu: your diff must be so painful you ALSO negrate
the author.
mircea_popescu: it is, yes.
the moment it needs a fucking 85 state machine
to interpret its meaning it is.
mircea_popescu: not when it comes
to clearsign, not when it comes
to vpatches, never.
text dude.
mircea_popescu: look,
the in-band problem i can sympatize with, but
the "let's
thus
turn
text into blobs" i do not.
a111: Logged on 2016-12-11 18:53 asciilifeform: so i had
two base64's png files in
there,
mircea_popescu: i don't want fucking "codepoints" in my life.
take your /x855 and shove it, bejaysus.
mircea_popescu: ah
the
thing where you
tried
to put A BINARY BLOB
through a PLAINTEXT!!!111 format and ended up having
to base64 it ?
mircea_popescu: "we don't use in band but we have not well formed diffs which you can't
tell"
mircea_popescu: if i go from "\\4hurrdurr"
to "\\4urr" you'll say what, \\4\4 ?
mircea_popescu: i'll give it a look ; but sounds
to me a lot like "rather
than learn vim i'll
try and make emacs adnotate"
mircea_popescu: perhaps
the correct solution is for code
to conform
to
the paradigm.
a111: Logged on 2017-01-05 00:04 mircea_popescu: i'm not fucking learning an aminoacid matrix
to be able
to use diff i
tell you
that,
mircea_popescu: i do not wish
to need
to know how many octets is
the blank lead of a new line
ben_vulpes: i could use proper docstrings at
that even
mircea_popescu: you put
them in
the new file.
they show up in
the patch
ben_vulpes: i did not realize
that
the patch could contain comments
that do not affect its output, is
that so?
ben_vulpes: mircea_popescu: aye, 'twas a step in
that direction
mircea_popescu: ben_vulpes slowly moving
towards literate code. here's a
thought... why not put
the comments straight into
the patch ?
adlai: "a privacy and fungibility focused cryptocoin
transaction structure proposal"
adlai: asciilifeform: incidentally, you may find
that /m/-w is a flail in
the general direction of "less snoreworthy ATC"
adlai: ah.
that
typo-collided collided with my other homework, which i am doing.
adlai wishes he could do
this homework instead of
that other stuff (integration by parts^H^H^Hhands)
ben_vulpes: is
there any sort of spec for "what difftron entails"?