122600+ entries in 0.032s
mircea_popescu: so might well have been forced mistake because of 2, even if in all likeliness satoshi put it in because of 1
mircea_popescu: best i can discern two things : 1) derp wanted to discourage old coinbases accumulating (had intuition about the blockchain bloat didn't want to address or know how to) ; 2) fees would have been HUGE early on without this, as in, "fuck you, you wanna transact it's 50 cents. i dun care your 1k btc is enough for a pizza slice ie 2 bux"
mircea_popescu: accept that or don't, i dun particularly care nor does in fact have any effects. but history is history, rather than fantasy.
mircea_popescu: and for the record, the reason we don't have an obnoxiously impudent mining cartel today is almost entirely due to that root, and its fruit.
mircea_popescu: yes, the proposition that "sane answer" === "i made a mistake" necessarily implies that as a precursor.
mircea_popescu: i'd guess a and esp b should be obvious. if they aren't obvious, the problem is almost certainly not what's stated.
mircea_popescu: asciilifeform a) yes i do "manual payments" ; this however does not mean i create the txn by hand. i'd think this'd be obvious ; b) any and all, this and all sorts of other resources are used to establish things about the network. i am, for the record, THE FIRST, and also for years THE ONLY both systematically sending txnfees "not needed" and pushing for others to do so. it is utterly not because i'm trying to shave pennies t
mircea_popescu: how the fuck is "sane answer" to be established via regexp with given string is what i want to know.
mircea_popescu: do that and let them starve, it'll count as a job well done.
mircea_popescu: woman's ONLY task is to protect her male offspring from this.
mircea_popescu: jurov is smart kid, gotta have some ankle weights of stupid and loud noises in inner ear lest he doesn't fit in with the idiots he originally originated with anymore.
☟︎ mircea_popescu: the whole nonsense unpleasantly reminds me of that sf story about a socialist future where people got "handicaps" to match their intelligence, lest they're smarter than their stupid parents / the runts in the litter.
mircea_popescu: no, not really, but "creating the controversy" might "help".
mircea_popescu: a) you see who deedbot trusts. that is called the l1. b) you see who l1 trusts. that is called the l2.
mircea_popescu: i dun care for the content, tbh. form will carry this matter all the way it needs to go.
mircea_popescu: the consensus in my head also is that if you keep with this whiny anal child subversive bullshit i'll bitchslap you so far up your mother's ass friends and family won't be able to reassemble the pieces.
mircea_popescu: aha. in fact i suspect both issues are present, and reciprocally reinforcing.
mircea_popescu: possibly. or alternately because nobody ever said "do it like this or i will fuck your children with many tiny bottle openers. in the eyes."
mircea_popescu: so it attracts a certain sort of stupid, not just in the sense of "a certain sort of stupid people", but actually a certain sort of stupid OUT OF people, even normally intelligent ones.
mircea_popescu: much like the bloviating bovines / paul biggars of the world perceive bitcoin to be "a safe space for their creativity" or somesuch, similarly build process.
mircea_popescu: but i think a large-ish part of hte problem is that build process per se is not actually specified.
mircea_popescu: in truth we've been working on all sorts of things other than build process for months nao.
mircea_popescu: diana_coman did we eat that up or what happened do you recall ?
mircea_popescu: phf eulora can't pull current cs because they fucked it up. so i wouldn't know.
mircea_popescu: anyway ; it's evident that in the future republican code will have one of the two possible profiles (trb-like ; eulora-like), not necessarily one, and certainly not necessarily the former.
mircea_popescu: ironically, it is also one of the most solid parts of the entire codebase.
mircea_popescu: nothing wrong with this. but also no solution to problem.
mircea_popescu: phf once management has put compatibility on your list of targets, you can say that all you want, best done in a mutter under own beard.
mircea_popescu: in other, unrelated-ish sad : to this day, "web development" has no javascript tree shaker.
mircea_popescu: except it will appear to, for a briefd interval at first. then it will create friction between purists and inclusionists, which is just about as dumb drama as livejournal disputes.
mircea_popescu: and trying to implement a "better" autoconf, even "by hand", will not result in anything better
☟︎ mircea_popescu: of course the process and its result will be horrifying.
mircea_popescu: ok, but i mean... so we drive nails with screwdriver because that's what we got.
mircea_popescu: heck, gcc is not much better than a three pass parser most of the time.
mircea_popescu: which really, isn't also parsed in the way lisp is also parsed because people are emotionally attached, and no other reason.
mircea_popescu: and parsing is uniquely inadequate for its task. in fact, its task is more adequate to compiling than c code is.
mircea_popescu: basically, seems to me most, or at least a good chunk of autoconf problems as described by alf come from the fact that it tries to parse, rather than compile. in the abstract sense of these terms.
☟︎ mircea_popescu: and sure, maybe d1 = "need to compile c code" in which case "check for d1" means "do we have a way to compile c code on this system ? ok, what is it ? and how is it invoked ? ok here we go then :"
mircea_popescu: let's work with an abstract example. suppose there's project X, which can for the purpose of configure be reduced to a list of n lines, whereby each line produces a dependency from the list of D1- D5 by the criterion that line# mod 5. so a sane autoconf will read the whole list, produce a list reading "d1, d2, d3, d4, d5" and then proceed to check these. once. five fucking checks, five lines of checking.
mircea_popescu: rather than "read line, check if we checked, check" wouldn't it be saner to "read all lines, create list of checks, check list" ?
mircea_popescu: i don't even understand why does it parse rather than compile, for instance. seems a very nutty design decision.
mircea_popescu: in any case, the whole discussion is about "something like automake" in the sense of "gimme magic"
mircea_popescu: oh what sweet delusion, "opengl will handle things for you".
mircea_popescu: this thing works. and it works in a very messy environment - gfx drivers, a raft of dependencies, etc.
mircea_popescu: this thing whereby noob sits down, pastes four commands off wiki, gets working game. every time.
mircea_popescu: ah, to clarify : i do not mean "automake". i mean the process.
mircea_popescu: that part's not so much in dispute. methinks i said above.
mircea_popescu: the metaphor breaks down on / depends on not noticing that IT DELIVERS.
mircea_popescu: if you know what the generator does, what's the problem.
mircea_popescu: seems pure fetishism. "i'm not signing generated code" well... yousigned ... your signature didn;t you ?
mircea_popescu being the derps in question nine cases out of ten. no fucking way am i going to chase obscure deps on your obscure project.
mircea_popescu: ie, anything that's different from the variety of keymashing they're used to from "work"
mircea_popescu: so far the major problem is irc usage ; and gpg/deedbot a very distant second.
mircea_popescu: asciilifeform do you understand the population of mouthbreathers out there is mystified by webirc page ?
mircea_popescu: actually ~every project of "battlefield" size seems to end up with a half mb to mb configure script.
mircea_popescu: had they properly used automake the problem wouldn't have existed.
mircea_popescu: they hardwired a bad path in there and i ran outof patience before finding the right magic knob.