217300+ entries in 0.124s
mircea_popescu: ben_vulpes you stiumbled on a fine example of "spreading-works". do not add coal
to soil you plan
to cultivate.
mircea_popescu: who
the fuck heard of
this, wood structure. bacteria eats wood.
mircea_popescu: i'm
telling you, if you somehow (which i doubt you did, but
taking you at your word) decided your soil's problem is lack of bacteria substrate,
then bone ash is what you want
to solve it with.
mircea_popescu: bone ash is pre-industrial. it's, for one
thing, how china was
traditionally made.
mircea_popescu: that's
the historical as well as correct solution for
that problem. spread it out before a storm.
ben_vulpes: mircea_popescu: oddly enough comes from
the "permaculture" wackjobs
mircea_popescu: ben_vulpes do
they sell calcinated bone as a fertilizer where you live ?
mircea_popescu: sounds like
the sort of bs
that works in
the lab only.
ben_vulpes: shit must work, first, because it was designed
to work.
touchy-feelie boob grabs come after.
ben_vulpes: correctness is not a
thing
to bolt on after
the fact.
ben_vulpes: part and parcel of
the "damn
the correctness, all attention
to developer uptake"
ben_vulpes: mircea_popescu: not according
to
the DSMIX
mircea_popescu: "As
there was no mechanism for concurrency control (except for minimal support for
things like counters), applications were often inconsistent" <<
then people wonder why us ships don't work.
ben_vulpes: where "decisions" ===== "the code i produced
that appeared
to work a few weeks ago"
ben_vulpes: sane and halfway intelligent folks refuse
to
touch it, so you're stuck with
the dregs and
their decisions.
mircea_popescu: see,
this is
the
thing with
these idiots, you can hire 8 of
them, and
they'll happily go
to work. on
THE PARTS of
the problem
that
they understand.
mircea_popescu: they ended up with unbounded complexity in
the "acl" system which really just happened
to be
the rug corner under which we brush everything we don't know how
to do, didn't it.
ben_vulpes: mircea_popescu: i
think
that's indices of just
the acl 'tables'
mircea_popescu: wtf is wrong wit hthese people.
the index
to data factor isn't a benchmark of efficiency.
mircea_popescu: "The object-level ACL system was highly inefficient. Numerours indexes were required
that could sometimes surpass
the actual data size by a factor of 3–4." << i guess i'm
the only one with production dbs where
the indexes are 90%+ of
the whole
thing ?
ben_vulpes: get excited about
things, support people.
ben_vulpes: coders support
tool diversity, of course
ben_vulpes: you have
to identify as "a coder"
to even consider
the stuff
mircea_popescu: i am
the fuck ahead of
the 8 engineers, and i'm not even a coder.
mircea_popescu: by now nobody actually has
the faintest inkling of a clue as
to how computers actually run. at all. whatsoever.
ben_vulpes: " if important customers lost data due
to human error, Facebook engineers would manually recover it from periodic backups"
mircea_popescu: there's
this film with
that inept idiot from whatever cars film,
the one with an adriano celentano like mug. he's supposedly
the capo of
this son-of-mobster inept douche and his main spoken line is something like "500.
that's how many bla bla".
ben_vulpes: persistence is slow and competence expensive, what is a sv fingertrap author
to do but eschew writes
to disk and hire
the lowest common denominator?
mircea_popescu: "Partial updates were problematic as small updates
to large docs got “write amplification” when being written
to oplog" <<< aaahahahaha.
mircea_popescu: "Slave reads were allowed for performance reasons" << check it out, apparently it's in
the sql spec after all. even on mondoshit >D
BingoBoingo: <asciilifeform> all i see is buncha sad folx in penal servitude, for some peculiar reason spending
their scarcely-existing free
time writing about
the wheelbarrows,
the dirt,
the scurvy. << lol, when
the weather warms up I may blog some on personal blog about wheelbarrows, dirt and anti-scurvy
ben_vulpes: anyone remember
the "no seriously flush
to disk" flag?
ben_vulpes: "i.e. writes were confirmed before
they were replicated"
mircea_popescu: who
the fuck. seriously now.
this made sense somewhere ?
ben_vulpes: mircea_popescu: wait 'till you get
to "what it got right"
mircea_popescu: and b) holy shit, 8 "engineers" ? kids with whispy chin-only beards stuffing
their
tongue up an asshole aren't engineers.
they're kids with whispy chin beards stuffing
their
tongue up an asshole.
mircea_popescu: er
term is "was butthole -
to - nose - fingered". not fucking planning.
mircea_popescu: "Backend was completely on Amazon Web Services •It was planned
to migrate Parse
to Facebook’s infrastructure (e.g. Haystack,
Tao, F4, Extended Apache Giraph, Gorilla) but
the project was abandoned •Roughly 8 developers working on SDKs, 8 on
the server, 8 DevOps + a few more engineers" <<< 1) no it was not "planned", fuckwads don't have mp certificate in planning, may not claim
they are engaging in any planning.
the prop
ben_vulpes: buddy if you get crypto involved in your drug production it can only be
to hose
the state, but w/e
ben_vulpes: mircea_popescu: you want random words in a string, you shoulda seen
the guy pitching "a cryptocurrency blockchain signature solution
to
the marijuana regulatory burden"
the other night
mircea_popescu: ben_vulpes listen, you're quoting a bullshit mfa
trying
to product place some inept dork. he did nothing ; is nobody ; random words in a string.
ben_vulpes: asciilifeform: ^^ is why you're reading
this
mircea_popescu: "Parse Server •Server was Rails at first (with 24
threads max. concurrency) with very little
throughput per server (~15–30 requests per second) •The server was later rewritten in Go.
The open-source Parse server is written Node.js and lacks many functionalities of
the original Parse server in Go." <<< holy shit, can you believe
the idiocy ? "we wasted a bunch of money doing stupid shit because we
truly believe"
☟︎ ben_vulpes:
http://btcbase.org/log/2017-02-10#1612725 << "It also
takes miners -- despite
their state of
the art equipment, access
to electricity, and cooling -- increasingly longer
to verify bitcoin
transactions" oh get right
the fuck out
tell
that
to
the myriad instablocks
☝︎ mircea_popescu: it's pretty much
that + "stories from around
the web -- find out
the secret glassblowers don't want you
to know about how a mother of
two in vincente lopez lost five kgs off her coffee mug each morning one weird
trick!"
mircea_popescu: where's
that cartoon about "hey guise, i heard about bitcoin/sex/eating/world yesterday, I AM HERE
TO FIX IT"
mircea_popescu: these fucktards, unqualified
to wipe
their own drool, dare dream of "revolutionizing
the way
that..." ? wtf,
ben_vulpes: and
to quote myself in another channel, "soz for cynicism but if it looks like madness and a
tower of abstractions written by frontend devs who don't in2 systems...it probably is."
mircea_popescu: "Technical problem I: complicated rate limiting. If limit exceeded by a factor of 60 for a minute, requests were dropped. Limits were
tracked using a shared Memcache instance. Consequence: when developers experienced rate limits in
the API,
they added retries.
The retries incurred enormous load in
the Parse backend." <<<
translation : "we are
three years old. wut is dis ?"
ben_vulpes: anyways, it never worked despite facebook buying and
trying
to make it do so
ben_vulpes: which
to quasiquote mircea_popescu "what is even a native mobile developer"
ben_vulpes: near as i can
tell, and it
tripped my retard alerts fast so i didn't invest much in determining how it works, someone used
that
to make a "database as a service" for mobiledevz
mircea_popescu: it's
that
the core parts of mordor infrastructure aren't even worth operating.
mircea_popescu: IT DOES NOT. it's not just
that "traction - 1mn apps, largest with 40mn users" means ~same as zip
ben_vulpes: bezos does
this
thing with
the
timeshare where he'll keep a virtual instance image warmish and boot it when
the rest of
the system says "hey we got a request for
that instance"
mircea_popescu: you are reading
this, asciilifeform , because in your head you imagine
the empire works.
ben_vulpes: asciilifeform:
to revel in others suffering ofc
mircea_popescu: the pain and suffering echo chamber resultant is supposed
to come as a surprise i guess ?
mircea_popescu: averagetard excepts
to crochet a culture out of what he sees on
tv and
tv expects
to crochet programming out of averagetard culture.
mircea_popescu: ustards, ever smarter
than
the next ustard, managed
to build
this system whereby nobody has
to do any work and everyone has hats
through stealing
the neigbour's. how
the fuck
that system's supposed
to work is anyone's guess, but here we go :
mircea_popescu: the problem with cultural appropriation as a content generation strategy is
that it only works if
there's a fucking culture in
the first place.
BingoBoingo: Apparently
they premised a
TV show episode around it
mircea_popescu: oh and in other lolz, i am apparently
the first
to have come up with "fakettorney" as far as google's concerned.
mircea_popescu: in other news, what
the fuck is a "blockchain developer"
ben_vulpes: drews: mod6 operates
thebitcoin.foundation, if you made
that
typo
mircea_popescu: aha. our democracy will do nothing better
than waste its resources.
mircea_popescu: asciilifeform
the idea is not without merit, whatever doubts in
the implementation.
mircea_popescu: or hm, strike
that. i dunno why but
the gpgfp/<fp> url 404'd for me. must have
typoed it