mircea_popescu: or alternatively, there's all sorta greatness, phf has a perfectly workable code metadiscussion system on btcbase, jurov had a ver yworkable one for earlier trb work and so fucking on.

mircea_popescu: because it occurs to me that ~if~ you publish your codebase you're working on, and if your blog works correctly in the mp-wp sense, then therefore you get all this for free, just make a metapost.

mircea_popescu: and so some other guy can go "that nfi part is just a discussion of so and so, like this" and so on ?

mircea_popescu: can you do this in some manner ? so people can follow your work if they can be arsed to import the same ide / cms ? (here, it's a bit of js, and a browser, that entire stack)

mircea_popescu: now admire what i can do : http://trilema.com/2013/internet-story/#selection-13.14-37.22 << this part is boring ; http://trilema.com/2013/internet-story/#selection-41.0-57.15 << this part is a quote ; http://trilema.com/2013/internet-story/#selection-61.0-65.37 << this part is about bitcoin ; http://trilema.com/2013/internet-story/#selection-65.37-89.175 << i have no fucking idea wtf this is.

mircea_popescu: responsibility is a fine and great thing indeed ; but it's not mechanizable, as part and parcel of why we have a wot as it is rather than as the lulzentreprise everyone else imagines it to be.

mircea_popescu: there's this lengthy list of examples of people coming to grief through the process of "that mp so dumb, dun even know how to horseride a shirt" or w/e such.

mircea_popescu: this pov is even voiced, but always in a chiding tone in training environments. it has its place there, but i dunno how practicable it is in the general.

mircea_popescu: diana_coman, i suppose in a very theoretical, idealized sense. in practice however... what are we to conclude on the basis of http://btcbase.org/log/2019-01-04#1884426 ? that neither i (nor anyone else here for that matter) had diffraction loaded in head ? the wave model of energy ? what exactly ? ☝︎

mircea_popescu: in any case the "i am of the republic, i will now base my self worth on the qty and amt of loading-in-head my works get" is, as of yet, a recipe for eternal sadness. this is a new rather than old republic.

mircea_popescu: but... what can you do. it's a crapshoot, you know this going in.

mircea_popescu: this is always a crapshoot.

mircea_popescu: what worries me is this approach whereby a) things tend to be discussed in response to some kind of prodding, and b) while that feeling lasts, only to c) fall back into an eerie silence within a few hours or maybe days, for WEEKS AND WEEKS AND MONTHS AND YEARS AT A TIME!!! ☟︎

mircea_popescu: because the republic's a practice, not a "narrative" aka daydream. fundamentally, what distinguishes us from the github hipster / foss moron / entire collected pile of avortons looking for their abortion from "the bay area" & portland to eudemocracia and beyond is that we don't read on the first pass, BUT ON THE SEC

mircea_popescu: this is exactly cosubstantial with the http://btcbase.org/log/2019-06-22#1919401 inquiry : "reading everything aforehand" as a strategy is just as dysfunctional as any other idealism aka premature optimization. there's a fucking reason republican doctrine is "do it by hand first, automate later, and those parts that actually need it and benefit from it, rather than randomly and abstractly like the pantsuit do". ☝︎

mircea_popescu: http://btcbase.org/log/2019-06-22#1919303 << this may work. my takeaway was that item could benefit from a little polish, a few choice one-liners added to documentation/comments, that sorta thing ☝︎

mircea_popescu: this isn't because "we're building housing for the sort of braindead morons who literally can not avoid walking into fire", but because "holy shit, spending life avoiding spurious pitfalls is such a sad way to go about things".

mircea_popescu: hewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iv/ spanning a coupla months.

mircea_popescu: there's on one hand the http://btcbase.org/log/2018-07-23#1837434 / http://btcbase.org/log/2018-11-27#1875247 / http://btcbase.org/log/2019-06-04#1917021 story arch, spanning a year. there's also the http://thewhet.net/2019/02/hanbots-cuntoo-bake-test-notes-part-i/ http://thewhet.net/2019/02/hanbots-cuntoo-bake-test-notes-part-ii/ http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iii-with-prep-script/ http://t ☝︎☝︎☝︎

mircea_popescu: trinque, do me a favour and also encrypt to http://wot.deedbot.org/208FE107E970F53262C4951232992F13CFA6CD06.asc so i don't have to wake up the girls to do ahlf hour of typing for me again

mircea_popescu: whereas if we decide we dislike the "packages" abstraction (and not merely dislike it a little bit, but quite a lot, enough to justify a lot of rewriting) then the available solution's to just make one big v tree. coming with the obvious problem that if indeed the whole world's just one tree, then trying to play BOTH duke nukem AND warcraft 2 will result in two copies of the kernel compiled, like if we were idiots.

mircea_popescu: in this context then, if we decide we like the "packages" abstraction, for whatever reason, the obvious solution would be to maintain ebuilds of various vtrees as packages, and emerge them into a desired pile together.

mircea_popescu: i suppose the one true break here, is that portage system actually excepts to build and link by bits. "out of the codemass intended to be used, arbitrarily selected portion A is built and linked first, producing object files, then B is built and linked against those binaries"

mircea_popescu: so is rather the problem that v-tron doesn't come with the right toolkit ? should get a tar and an interface for make ?

mircea_popescu: understanding's not a mechanical task.

mircea_popescu: this seems a fundamentally bad deal to me.

mircea_popescu: ious a consideration.

mircea_popescu: i mean, maybe all local wot failed to sign a patch portage deemed essential so it downloaded it from power-rangers.net. yes ?

mircea_popescu: that also wouldn't be a trb server, practically speaking.\

mircea_popescu: trinque, let's go at this a different path. what would you even do with a trb ebuild ?

mircea_popescu: you understand this, yes ? there's no definite utility to computers. for all the promises of grandeur and wunderbarness, a gun's a gun's a gun, and a computer's a smartphone's a tivo.

mircea_popescu: asciilifeform, there's nothing to do between a gun and a computer. a gun is a tool. a c omputer is a piece of shit.

mircea_popescu: trinque, if everyone includes ebuilds of everything and in a few years' time everyone's just doing portage because "it's easier, man" ima be very damn sad. ☟︎

mircea_popescu: no, because who gives a flying fuck already.

mircea_popescu: but it's a mitigation, if i wanna know i gotta look.

mircea_popescu: the fundamental problem here is the implicit dwim-ism involved in "i don't have a vax/dec/cuisinart, i have a COMPUTER, as in the abstract"

mircea_popescu: if tomorrow we have a ffa-for-pc and a ffa-for-mips alternative, there WILL BE AN IFDEF.

mircea_popescu: to do the "ifdef vax" in a magically acceptable manner ?

mircea_popescu: and your solution seems to me a bit of smoke and magic, because what will you use to manage "which v tree, dec or pc" ? a vortage ?

mircea_popescu: well yes, but look here : at some point we decided to save the state of computing, specifically to avoid this "nobody has built since 2011, here have a virtual machine"

mircea_popescu: i've not looked in a long time, myself.

mircea_popescu: i personally doubt such a thing as a lisp portage can be made. but then again i have no coding experience.

mircea_popescu: trinque, do me a favour an' state the problem in yoru own words so as to see how synced we're here

mircea_popescu: he has a point there, in that at least portage will emerge a complete world, for whatever any other complaints one might harbor

mircea_popescu: and yes indeedy, i'd much rather mandate a "your project must buuld on gprbuild" than a "your project must include ebuild", if there's mandatin'.

mircea_popescu: the fundamental problem remains, however, that a sufficiently large c/cpp code snippet will not build on any machine.

mircea_popescu: i am not even disputing that. i think large projects (ie, again, eulora) used it as a ... well, default evil. "gotta use something, wtf can do".

mircea_popescu: and the reasons we wanted v were very much specifically and centrally "so such a thing as portage is can NOT be had, and such problems as it solves can not be solved"

mircea_popescu: what's a package, even ?