20000+ entries in 0.012s
mircea_popescu: btcbase.org/log/2018-10-15#1862927 ; and similarly ANYTHING ELSE. the bar strictly is "more than three people get together who aren't mentally subnormal". that's it!)
mircea_popescu: "As they succeeded, the cool is gone" << so fucking true!
mircea_popescu: BingoBoingo is there some subtext of "hey, anyone wanna finance my becoming a grower" in there ?
mircea_popescu: BingoBoingo it does go pretty faint, the respiration. which yes, can definitely panic the more medically-informed.
☟︎ mircea_popescu: bwahaha. good thing hilary clinton gave them their rights!
mircea_popescu: "ruderalis plants reservoir " << you're missing a verb.
mircea_popescu: it's kinda funny how the predictable result of an hour's logs is that... "hey guise... there's even MOAR space at the trough than we thought! you have engineermanyears to put to some use ? ohohoh here, here, uses, pick, choose!"
mircea_popescu: asciilifeform i thought trinque was doing that exact thing for the linux machine.
mircea_popescu: (and the experienced historians among the "anyone" guessing will point to -- HIDDEN EXTERNALITY!!! as fucking always! they hijacked their conversation channels to repeat over and over AND OVER again "if you want it -- write it", ie, "the cost of portability, as the backflow of using stupid hardware, is hidden under the rug tee heee")
mircea_popescu: how the fuck they managed to live before, uncomputable-cost-portability herp derp is anyone's guess.
mircea_popescu: after us, it is a stable, sustainable and sane item, two data points : "to get x you burn y, make a call"
mircea_popescu: ie, before us, "portability" was an abstract nothing, single-datapoint debalanced nonsense, like "the pursuit of happiness" or "safety first" or "no means no" or whatever other fucktarded pantsuit nonsense.
mircea_popescu: ussed is worth having, why do you think maintaining the respective branch is too much work ?"
mircea_popescu: asciilifeform to go back to that thread : i suppose the "portability" discussion is deeply broken in empire (and no, linus, rms and friends aren't "a republic of their own", they're leningrad school and naught else). consider how
http://btcbase.org/log/2018-10-15#1862894 drives the dilemma : "if the trouble of maintaining a tree is not justified, why do you think the iron discussed is worth having ? if you think the iron disc
☝︎ mircea_popescu: the puzzler of all time for the average fetlife-grazed chickie, too. "wait... you mean to tell me ~you~ don't really care to talk ~to me~ ?!@?!?! but pantsuited hilarity gave us our rights!!!" sorta "this development goes neatly against everything i've been told to believe."
mircea_popescu: because yes, there very much is such a thing as a bar for civilisation, or at the very least for conversation. ~could~ talk to anyone, much like ~could~ very much shit outdoors ; but one strangely enough discovers in a short time that... doesn't really want to.
mircea_popescu: and this started after eg mpoepr's ~exhausting the live ponds.
mircea_popescu: soon thereafter returned, very puzzled -- why doesn't $x ever wash ?!"
mircea_popescu: i suppose they do create some obligation, as per ye olde "if you can -- you must", in the sense that much like girl can't imagien why she'd mate with dood who doesn't use soap, i can't imagine why i'd talk to dood who "has ideas" or w/e they call being filthy outside the walls.
mircea_popescu: not that anyone has to use them for any purpose. but -- they do indeed exist.
mircea_popescu: anyway, whole point being that we have elaborate research-driving/agreement-building & history-preservation tools.
mircea_popescu: then later, when he had the time for it, or when others saw the wisdom of the point after his death, or whenever, that stub could've been replaced with the proper item.
mircea_popescu: so -- looking back to the crc32 situation, suppose that for whatever reason the consensus wasn't "yeah, should definitely have both" but "division is stupid, only tables are needed". at that juncture, ave1 could have made an alternate patch to the crc32-lookup consisting of merely a changed manifest, saying "Hey, for so and so reasons I think this should be a crc32-division, I intend to do it later."
mircea_popescu: eulora is so much fucking nicer when you wake up to a working foxybot!
mircea_popescu: could work like !Q later tell == !Q 0 tell ; otherwise !Q 144 tell
mircea_popescu: not clear to me if caching shenanigans or what. but anyways.
mircea_popescu: specifically what i mean : if a process creates/deletes file on a very narrow schedule ; and another checks for file's existence on very narrow schedule, their respective pictures of when they think file exists and doesn't fails to match up.
☟︎ mircea_popescu: listen on a raw socket. otherwise you're prolly getting what comes out of pf_packet, which is a packet.
mircea_popescu: "raw packet", "raw frame", rawdog, etcetera. tcpdump/libpcap-likes tend to dump the packets not the frames.
mircea_popescu: but are you dumping the raw frames ? or are they reconstructed the "indended" packet for you ?
mircea_popescu: tree A is single if there exists a "most extensive press" that includes all possible presses are included ; tree A is multi if no such MEP exists.
mircea_popescu: eg, branching the eucrypt tree over embeds/mainstream is (possibly ?) sustainable ; whereas branching it over "joe needs a project to direct to justify his employment with shithat" is exactly as sustainable as post-2018 linux.
mircea_popescu: which is the fucking problem with current versioning systems, they encourage illegitimate context creation, of the sort of "i need to publish or perish therefore let us rename biology and rediscover it".
mircea_popescu: in any case historically this ~exact process~ is how eg djb ended up with the modicum of respect he then proceeded to squander.
mircea_popescu: in fact, a very solid basis for respect is, "whenever i sit down to rewrite x, i end up writing what he wrote ; whereas whenever i sit down to rewrite y, i end up using empty page. thus therefore x is rated 5 and y -10"
mircea_popescu: asciilifeform in the end we could phrase it as "some rewriters -- deeper than others".
☟︎ mircea_popescu: imo this "empty buffer" notion is leftover implanted brain electrode from ustard academia/schooling. "oh, gotta be original". no such fucking thing ; and the only reason they talk about it is to keep intelligent people from doing important work.
mircea_popescu: nor does such a thing as "empty buffer" truly exist, nor is it any kind of substantial distinction, and so on.
mircea_popescu: this is 100% "read and rewrite" and entirely and absolutely NOT copy/paste.
mircea_popescu: 32 is a very simple thing and absolutely easy to lift and package into 52 lines of code in the .adb file + 130 in the .ads file so 182 all in total1, comments and two types of input (string or raw array of octets) included."
mircea_popescu: to quote, \"As usual, the forum quickly pointed me in the right direction - thank you ave1! - namely looking under the hood of course, in this case GNAT's own hood, the Systems.CRC32 package. Still, this package makes a whole dance of eating one single character at a time since it is written precisely to support the stream monstrosity on top rather than to support the user with what they might indeed need. Happily though, CRC
mircea_popescu: v-tree lives through wot and through wot alone, it's not some kind of self contained magic.
mircea_popescu:
http://btcbase.org/log/2018-10-14#1862400 << #1 thing you do, is you TALK TO PEOPLE! there is no jwz way out of politics. if regrind hurts you, tell them not to fucking do it ; and if they won't listen tell whoever will listen to not follow the new thing. and so fucking on.
☝︎ mircea_popescu:
http://btcbase.org/log/2018-10-14#1862397 << because cut-and-paste was never contemplated as a possible alternative, it was read-and-rewrite. because moving from one tree to another is exactly translation, one must bear in mind context and only implement ~the algo~. consider how we got crc32 -- we did NOT cut-and-paste from anywhere. diana RE WROTE IT!
☝︎ mircea_popescu: kinda the fucking point, building yggdrasil over here.
mircea_popescu: in any case, type1 might get i dunno, later-patch-taking-advantage-of-ddram whereas type 2 might get later-patch-needed-for-old-arms etc.
☟︎ mircea_popescu: but while there's overlap of people contributing to both type 1 and type 2 branches, it's more likely the situation will continue unground.
mircea_popescu: IF the groups ever diverge absolutely, they MIGHT eventually re-genesis the thing, making all leaves 1...n into a unified genesis and continuing from there.
mircea_popescu: the leaves downstream from EACH n1 needn't be identical, nor needn't be different. in effect, the tree now has TWO groups of maintainers : those who maintain type 2 tree, for embeds, will not === those who maintain type 1 tree, for general use.
☟︎ mircea_popescu:
http://btcbase.org/log/2018-10-14#1862386 << not at all! there's two possible ways to implement crc32 : with lookup tables, and with plain division. these are mutually exclusive. type 1 is faster, and therefore mainline. type 2 is smaller, and therefore of interest in certain contexts. therefore, at leaf=n, one has to chose : either n+1 type 1, or else n+1 type 2.
☝︎