101500+ entries in 0.064s
mircea_popescu: asciilifeform, remember
that
time we needed like 100kgs worth of sheet metal profiles, ended up having
to fly
them over with white man's airship because local orcs can't bend metal along predetermined lines ?
mircea_popescu: la franquicia para compras por internet de particulares uruguayos <<
the franchize for internet purchases FROM local private parties is
the correct solution. but not only did
they lift
the bureaucratese,
they lifted it wholesale, "de" now means "of" like english works, because why
the fuck not, soberania.
mircea_popescu: (anyway, i'm mostly joking.
THEY don't know how
to speak
their previous colonizer's language, and so
they say "to buy from locals" when
they mean "the buying of locals". w/e)
mircea_popescu: local fermented beverages, how
the fuck do i know what orcs
trade.
mircea_popescu: holy shit,
the retards. not only are
they ever going
to use a "smart"phone
to go on a website,
they DON'T EVEN FUCKING KNOW HOW
TO MAKE A WEBSITE ANYMORE.
mircea_popescu: batshit insane fucking system
they got, incidentally. why not just make a govt amazon, force locals
to use it if
they don't wanna pay
tax.
mircea_popescu: by
the
time
they're bringing out
the "ampararse" and "franquicia" you know
they're blowing bubbles out
their ass.
mircea_popescu: "Si usted no desea utilizar uno de los 3 cupos que
tiene con la franquicia para el año, dicho envío será liberado abonando impuestos."
mircea_popescu: if you want
to
take advantage of
the ... "right"
to buy from local individuals (3 items per year)
a111: Logged on 2017-10-02 11:16 diana_coman: Framedragger, did you ever publish somewhere re
the customs fee you had
to pay for your fg(s)?
mircea_popescu: cuz it's furry, see ? and it jumps around. LOGIC from
the mothership.
mircea_popescu: really now, a 6 foot 5 dude
that evolutionarily exists
to outrun
turkeys in flight ; a 4 foot pigmy
that evolutionarily exists
to fit comfortably under elephants and poke
their belly with a spear from underneath and some fat government worker are "the nation of Africa" ? for
the same money
the average sex of mankind is rabbit.
mircea_popescu: but srsly now,
this whole "race" mental cockroach, especially when by "race" is meant
things like "the nation of africa" (really bitch ? every saw a guy from senegal ?) or "asia" or whaterver
the fuck is SO
transparently a redditard's ploy
to put
the world
through
the juicer and get "just
the facts" out, preferably in
the same sort of ram buffer his middle school education required, which is four pictures and five bullet poin
mircea_popescu: a degree of mental confusion roughly similar
to calling people from ohio mexicans because you saw one in a hat once.
mircea_popescu: but you can generally
tell
these all come from
the same source
the conceits of "racism" or "democracy" come from. because what
the FUCK is "asian" even ? a notion similar
to "ant".\
mircea_popescu: not afaik ? ~this~ is
the classical.
the "black power" stuff is it with
the colors swapped neh ? like "cocoa milk, in case you were getting bored with all milk beinbg white" marketing
thing ?
mod6: Still raining
there?
mod6: Ahh. Yeah,
the good news of
the bad news huh.
BingoBoingo: The productive cough is more productive, but at least
the color is substantially improved
mod6: How goes
today BingoBoingo?
mircea_popescu: inb4
the next mosul lulz (aka "great success of barefoot negresses on
the world diplomacy stage") will be
the coallition capture of rebel islamabad.
trinque: ah maybe, can go in
too. oughta be minimal crud, and clearly contained in one function. couple of whatever
they call
the implementation identifying macros.
trinque: (think, when
this is done, we have a basis for a vtronic lisp repository, aside a vtronic portage, and all
the rest)
trinque: v doesn't import
the imperial convenience idiocy. it eats
the world from where it stands.
trinque: worth saying also
that use of quicklisp is anti-v. it's a wad of packages some dude compiled, he's not in our WoT, no signatures on packages (last I checked), and
to
top it off, it hauls down foreign code and executes for you as a single op.
trinque: I'm fine with helping. could
take a crack at it
tomorrow.
trinque: can implement a "run-program" of our own in here, implement for sbcl and ccl. I don't know
that I've heard of anyone here using another.
trinque: wise
thing
to do is muntz off
these foreign entanglements. v needs
to stand on its own as much as possible, and ever more so.
mircea_popescu: esthlos, people
throwing
their hands in despair over something [they
thought] you said is always way
the fuck preferable
to people
throwing up
their hands in despair over something you did -- specifically because
there's a lot more room
to misinterpret what's said
than what's done.
trinque: the parsing here is pretty simple, oughta be able
to implement without hauling in a big honking dep
trinque: I'd also like
to see
the cl-ppcre dependency drop (not only for
the call out
to quicklisp
to obtain it)
trinque: the communication gets easier
the more you work it, so stick around
esthlos: also want
to say
that above confusion was mostly misinterpretation of various comments on my part. not about what "v" is _now_, but on what was being asked of me
esthlos: i'll field and questions/criticism
tomorrow, gotta run for now
esthlos: trinque: no, I didn't jump off
the deep end without discussing it. I've already made
the interface changes
esthlos: mircea_popescu: i'm at a loss of what
to say. but really, it's moving
trinque: it'd be a happy
thing if I can stay with my welder in portage's innards while
this happens and not have
to end up doing
that part myself
trinque: I intentionally aimed you at "fix
the interfaces" because it appeared
that was
the
thing most glaringly wrong with it, and not all
this
trinque: esthlos: so at least less
to change about your v-tron right?
though definitely *read*
the others so you're more certain you understand what
the
thing is.
mircea_popescu: well yes, but you don;'t have
to be. i get it, in general everything's crap, but dja
think i'd even for a second have permitted it if it were ?
the stuff about, it's all stuff
that somehow survived
the republican demolition frenzy. it's not just random gunk.
mircea_popescu: they're
there
to help, not
to hinder, all
the accumulated piles of previous materiel. or does
this not seem so ?
mircea_popescu: but doesn't
the sadness of solipsism strike you ? it's not hard enough
to have
to go
to war, you'll do it naked and barefoot and hope you can find some flint
to make a spear before
the vietcong finds you and gangrapes you ?!
esthlos: and wrt self hatred, I'm really at a loss. somehow it
thought like a good idea
mircea_popescu: the idea was
that it'd work passively
to determine order in afore-ambiguous situations.
esthlos: mircea_popescu: what I
took away from your comment was
that
the philosophy file was
to be used
to determine vpatch ancestry, rather incorrectly it seems
mircea_popescu: crossdressing, for all
the social stigma, cruising highway bathrooms looking for glory holes, for all
the infection potential, sitting by a wall and banging your head against it,
they're dubious behaviours, yes, but
this fucking
takes
the cake. what, you hate yourself QUITE
TO
THAT DEGREE ?! why ? what did you ever do
to yourself
to
take such umbrage with yourself ?!
mircea_popescu: esthlos, what sort of barbarian, orcish, utterly insane and self-spiteful approach is
this, whereby you set forth
to do a
thing without understanding
the previous iterations of
the
thing you're doing ?!
mircea_popescu: apparently in my naivite i bestowed upon
trinque a larger dollop
than originally realised.
esthlos: ben_vulpes: no, actually
that's part of what asciilifeform encouraged me
to do
a111: Logged on 2018-05-06 23:21 esthlos: alright. What I don't understand,
then, is mircea_popescu's response
mircea_popescu: aanyways ; i agree with
trinque in
that
the "history file" needs not be considered by
the v implementation as anything in particular. it's a usage convention not a special case.
trinque: aha, I haven't a clue how he got
to "thus can merge"
a111: Logged on 2018-05-06 23:13 esthlos: if
the new V defines
the current state of
the project as a single hash,
then multiple parents (such as h, i, d, and j) becomes impossible
trinque: if I
tell
the
thing
to press
to a signed patch, it should press, history file edited or not.
trinque: only
thing
that a V would even conceivably do related
to "history" is indicate in "flow"
that certain patches are not mainline, for lack of a history file edit
trinque: please do not
try
to attach complexity barnacles
to
the history file, because it seemed very important in logs, or something.
trinque: esthlos: if I
thought you'd gone
that far afield, I would've asked you
to do all
this instead of a simple cleanup of interfaces
mircea_popescu: esthlos> looking
to cement understanding: with current V, file-level merges are impossible << huh ?
esthlos: alright. What I don't understand,
then, is mircea_popescu's response
☟︎ trinque: and it so happens
that one is a history file.
trinque: parenthood is determined by
the graph of patches as created by walking across
the hashes *per file*
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ;
the emerging consensus is
to have a dedicated philosophy file which a) all patches must
touch (by protocol) ; b) contains comments as
to
the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated.
the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going
to coalesce around a variant of whatever he uses.
a111: Logged on 2018-01-23 12:09 esthlos:
to determine if b.vpatch descends from a.vpatch, my idea is
to scan
through b.vpatch and ensure
that each ---(file,hash) matches some +++(file,hash) in a.vpatch. is
this
the standard procedure?
trinque: the graph will still look similar
to
the png you linked, but with a singular line also running
through it
trinque: sections of a given patch will yes, be parented on
the previous, in a straight line, but
this does not at all mean
that
the patch doesn't *also* have other parents, following
the antecedent lines of
the other files
trinque: it is a fact about correct operation of a V, and perhaps a V client does something
to help
the operator along "hey you didn't edit
the history file, wild patch!" but does absolutely nothing differently. it's just another file.
trinque: you should ignore
the "history" file notion entirely; it has no bearing on how your v-tron operates
trinque: it doesn't, so how did you get
there?
esthlos: if
the new V defines
the current state of
the project as a single hash,
then multiple parents (such as h, i, d, and j) becomes impossible
☟︎ esthlos: I
think I understand,
though I may be being
thick. what I'm describing is differnt
trinque: if I haven't addressed what you're
talking about
though, please elaborate.
trinque: and
this is appropriate.
the way
to solve
the problem of "have
to edit something in each desired antecedent" is
to do
that, edit something,
the history file
trinque: in current V, j had
to *edit* items in both h and i
to keep
them in
the set of pressed patches, if pressing
to h
trinque: this oughtn't be enforced by
the V implementation. operator might fully intend
to *not* include a patch in
the formal history of
the project
trinque: the history file is indeed
the chosen solution
to
the problem of
tree fragmentation. all patches which are intended
to have permanence in
the v
tree shall edit
that file.
trinque: current V presses
the patches walking upward from
the "head" given as a parameter
trinque: esthlos:
that's incorrect, current V does not press all leaves
esthlos: so is
this what's desired, or am I off
the mark?