38500+ entries in 0.863s
mircea_popescu: "While authorities begin the painstaking work into why gunman Omar Mateen massacred at least 50 people at a popular gay nightclub in Florida, they'll have a number of clues for understanding the mindset of the mass murderer" << guy didn'
t care for your stupid cult ?
Framedragger: mircea_popescu: 10000 mile distant response: just because you accept (at least parts of) (berkeleyan?) skepticism doesn'
t necessarily mean that *all* relevant conceptual boundaries are useless and prone to slippery slope dissolution
mircea_popescu: it runs into a problem of "what it means to be provided by universe". for instance - is failure of socialism provided by universe ? is the fact you can'
t walk through fire conventional or universal ?
Framedragger: i don'
t know, but either (1) do not distinguish, or (2) use asciilifeform criterion, which i don'
t think to be circular, i.e. it's probably sound?
mircea_popescu: sadly i was otherwise involved at the time and didn'
t think to shoot it up.
mircea_popescu: honestly it doesn'
t seem anyone has a better idea of what a spec is than "correct metaphora", which is ridiculous, ironic, scandalous and not much to go on simultaneously.
mircea_popescu: asciilifeform anyway, your definition of a spec is amply vulnerable. take the time issue : what, ddr can'
t be specified ? fingering a girl neither ? what happens if the spec asks for a 10 followed by a 11, and ytou get the 10 and silence ? now you got a whole halting problem on your hands.
a111: Logged on 2016-06-14 13:18 mircea_popescu: there's some problems with the concept of "specification" also that i don'
t have clear in my mind
mircea_popescu: asciilifeform well, for any possible output, it'll get either accepted or rejected. doesn'
t get clearer than this.
mircea_popescu: "don'
t steal" can not be a spec, only "if you steal you go to jail" ?
mircea_popescu: there's some problems with the concept of "specification" also that i don'
t have clear in my mind
☟︎ mircea_popescu: i posit that no matter how good a job you do of it, and i believe you capable of an exceptionally good job, will never be perfect, because it can'
t be for fundamental reasons.
mircea_popescu: i do not wish my os to contain as much as a fucking variable declared i don'
t use. not one.
mircea_popescu: asciilifeform i wouldn'
t use it in my creations without reading it. i may run it on a box on the basis of wot though.
a111: Logged on 2016-06-14 05:18 phf: but i haven'
t seen those problems yet in the bitcoin codebase, the problem that i did see is a certain deliberate apartness of tinyscheme related code, that subtly violate my assumptions in a nagging way that i described above.
trinque: why isn'
t my program only the set of code it actually uses
trinque: funny thing here, isn'
t lisp supposed to be able to manipulate its own damned code
phf: but i haven'
t seen those problems yet in the bitcoin codebase, the problem that i did see is a certain deliberate apartness of tinyscheme related code, that subtly violate my assumptions in a nagging way that i described above.
☟︎ phf: i think that a lot of these conversations come to a standstill because they deal with infinities, rather the shaping into a reasonable concrete. it seems proper that slapping new code onto bitcoin should come in a form of wot signed balls of mud, that don'
t particularly care about preserving all information and pedigrees and such. "i wrote this new math function and it uses this mp code that i lifted elsewhere but shaped enough that only relevant bits remain and for all practical purposes all you see in this patch is all that matters"
phf: fwiw, we don'
t have examples in code base of 1000 re-readings but we already have an example of openssl, which is where this conversation started
mircea_popescu: or for that matter, anything you don'
t feel like reading.
phf: i prefer to just loosen the requirements a bit. a failure in a vpatch doesn'
t need to result in public disgrace, shaming or execution. that might be one of reasons why work came to utter stand still, nobody wants to "sign off" on this or that like it's going to end in the style of diana_coman's story
trinque: point being that problem would be trivial if we weren'
t introducing human-side optimizations like #include and general libraries of 100s of functions out of which you pick a couple
mircea_popescu: you can'
t fucking have "nice things". deal with it!!11
trinque: question wasn'
t (I thought) how V works, it's whether #include is a useful tool or a festering fucking sore
trinque: doesn'
t this run directly against your fits-in-head thing?
trinque: I didn'
t read it; I just copied and pasted that hash from shithub
mircea_popescu: asciilifeform not in the slightest. you ever read a novel TWICE only to discover that hey, i hadsn'
t gotten it the first time ?
mircea_popescu: v exists SPECIFICALLY so you can'
t "save labour" in this manner.
mod6: in way that asciilifeform lays it out, in the sense that this vpatch would start from 'false' and end on 'SOME_HASH' and create a file(s)|directory(ies) that did not previously exist, then yes a 'genesis' but only on concept - not in name. as we shouldn'
t not confuse the two imho.
mod6: don'
t worry about that. paint me a picture on how you might go about the task - how and where does
t.pl go? or v.pl ?
mod6: so what would your implementation look like here? a patch to a current leaf of the trb patches that inflates say
t/
t.pl from 'false' on the end of the trb 'light-code' ?
mod6: don'
t add nsa's key to your wot, and you wont see that patch right?
mod6: let's say that i have this project called `
t'. and I'd like to make it readily availble and a genesis for this specific tool.
mod6: im fine with this too -- alf sees this as a mistake. so just thought I'd take a minute to address the alternative. unless there is something that I haven'
t considered? asciilifeform? suggestions?
mod6: one inflates the trb universe into bitcoin, the other into v. i guess it doesn'
t have to be that way.. v-genesis could be added later on down the line as a leaf node. but then it probably shouldn'
t be named "genesis" as that seems to break the convention.
mod6: so i kinda see this in two ways. either i place v/
t/whatever into /v/ and we have many multiple roots, inwhich case when you pull from the mirror you end up with the following dirs: bitcoin,
t, v, whatever, ... or we can break this up into multiple projects.
a111: Logged on 2016-06-13 23:43 mod6: Which also means, it almost makes no sense to even publish the v-genesis.vpatch that I currently have as it is no use to anyone if they can'
t grab a canonical version from the mirror. All they'd be able to do is get it from the mailing list, with the seal, and drop it into their local working directory as one would expect.
a111: Logged on 2016-06-13 23:43 mod6: Which also means, it almost makes no sense to even publish the v-genesis.vpatch that I currently have as it is no use to anyone if they can'
t grab a canonical version from the mirror. All they'd be able to do is get it from the mailing list, with the seal, and drop it into their local working directory as one would expect.
a111: Logged on 2016-06-13 23:39 mod6: and since now we have; trb,
t, v, ... and many others probably forthcoming, one should need to specify what they want to pull down locally.
phf: but yeah i don'
t imagine any of that stuff is reusable after a burn
phf: well, since it sounds like we're both talking from burn build experience, some people get impact drills and some don'
t. if i overtorque i just put a second one next to it. it's not pretty, but it ensures that bunch of drugged out hippies can do somersaults on the thing
ben_vulpes: kinda like the "don'
t break and turn" at the same time mantra.
phf: BingoBoingo: i think there are cases where impact driver applies, like if your bit gets stuck in metal, and you want to power through it, but like others said, don'
t drill metal with general bits. i've used impact driver on large wood builds and it's a joy to use, the torgue makes for a very rapid but controlled coupling. i think i might've grabbed one to do drilling in a pinch, but i wouldn'
t say i noticed much difference one way or
mod6: arg. what a long day. can'
t believe it's already the thirteenth
mod6: <+mircea_popescu> you can'
t say lisp without S! << heheh. "lithp"
mod6: %a
t F "Add Long Notes Feature" "Implement functionality so that users of
T can create notes longer than 300 chars if necessary."
mod6: %e
t 1 S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t." 2
mod6: %e
t 1 S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t." 1
mod6: %a
t S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t."
mod6: %e v 3
T "Update Tests" "Update V cucumber tests for 99994 with specific testing around separate projects." 4
mod6: %a v
T "Publish V-Genesis" "Publish V-Genesis post 99994 release." 1
mod6: %a v
T "Update V" "Implement ability for V to pull separate projects from the mirror based on hash (or possible alias)."
mod6: %a v
T "Update Tests" "Update V cucumber tests for 99994 with specific testing around separate projects."
tb0t: Ticket Type Codes: C => CHANGE | D => DEFECT | F => FEATURE | I => INVESTIGATE | R => REFERENCE | S => SAGA |
T => TASK | X => DOCUMENT
mod6: Which also means, it almost makes no sense to even publish the v-genesis.vpatch that I currently have as it is no use to anyone if they can'
t grab a canonical version from the mirror. All they'd be able to do is get it from the mailing list, with the seal, and drop it into their local working directory as one would expect.
☟︎☟︎