log☇︎
292600+ entries in 0.177s
asciilifeform: and the problem was solved in ways which mircea_popescu would find quite unsatisfying
asciilifeform: and 'the implementation was the spec', at least for a long while.
asciilifeform: where lathe men had considerable trouble specifying threads ~on paper~
asciilifeform: re the ~original~ specs of the 1700s.
asciilifeform: did we ever do a screw threads thread ? ☟︎
asciilifeform: i actually own some of the trees the killed.
mircea_popescu: so the phone grid can't be specified ?
asciilifeform: (i.e. individual telephone sets, but not 'the phone grid')
asciilifeform: normally, ones you can throw out if they fail.
asciilifeform: whole concept of spec only makes sense in application to testable man-made objects
asciilifeform: if scale small enough - then surely not satisfactorily.
asciilifeform: 'relates inputs to outputs' does not exclude time, voltage, sex, whatever.
asciilifeform: you can put whatever you want in a valid spec, so long as it is deterministically testable.
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: serbia, ~did. anyway, to round up this excursion : http://btcbase.org/log/2016-06-14#1482607 ☝︎
mircea_popescu: but that's neither here nor there re our problem.
asciilifeform: to the extent that bitcoin does ~not~ behave this way, it is broken design.
asciilifeform: like going wrong way in traffic will kill an idiot
asciilifeform: at any rate, spec is a weak animal when it relies on promise, rather than protocol. ideally you want a simple litmus test for conformance that insta-zaps deviants
asciilifeform: did say 'unambiguous' and testable
mircea_popescu: care to revisit your definition of a specification ?
asciilifeform: or dragon-presence is not a testable thing.
asciilifeform: ~i~ ought to be able to summon dragon likewise.
asciilifeform: 'dragon came for me from this here well, ergo it contains dragon' is not an objective test
mircea_popescu: but hey, you test it. "as best you can". then nobody believes the results
mircea_popescu: you didn't say that, either.
asciilifeform: how do you test the network ?
asciilifeform: a spec must be objectively, deterministically testable.
mircea_popescu: o god almighty he was playing it straight. listen asciilifeform you'll say the exact same thing about your bovaric contraption down the road. "the program is fine the world failed it". need i quote brecht to you ?
mircea_popescu: i hope this was deliberate joke yes ?
asciilifeform: my definition is fine, you are trying to apply it to a dog vomit
mircea_popescu: you did not say that.
asciilifeform: rejected today, accepted tomorrow.
mircea_popescu: asciilifeform well, for any possible output, it'll get either accepted or rejected. doesn't get clearer than this.
mircea_popescu: experimential specification, "send a txn see if it makes it through".
mircea_popescu: but the network already and very clearly specifies inputs nad outputs. this meets your definition.
asciilifeform: the wild animals of the forest are not a spec
asciilifeform: since i did not mention timings or analogue characteristics, the two will be equal per the spec.
mircea_popescu: so you've just said "the bitcoin newtork is the bitcoin specification" here.
asciilifeform: absolutely. i can build machine to match my spec above out of GaAs transistors, or MOSFETs on Si or whatever.
mircea_popescu: then variant and unequivalent implementations of the same spec may exist ?
asciilifeform: all specs are maximally prescriptive. in that implication is 'if you don't do x, you are not conformant and we throw you out and buy a new you'
mircea_popescu: "don't steal" can not be a spec, only "if you steal you go to jail" ?
asciilifeform: e.g., 'the box takes 8 bits as input and sets the 3 bits of output as equal to the number of 1s on the input register.'
asciilifeform: it is sufficiently detailed and unambiguous that unrelated groups can and have implemented fully compatible compilers.
asciilifeform: have an example of correctly made spec: the ada ref+rationale.
asciilifeform: spec ain't magic. and much of what you see passing for spec is a deliberate attempt to paper over broken ~concepts~ with verbiage.
asciilifeform: meat sucks to begin with, 'crooked timber' etc.
asciilifeform: no such thing, because spec is a program for ~meat~
mircea_popescu: no generally. the definitive, absolute and no sharp edges or loose parts version, that can be engraved into the ether and forever work without change.
asciilifeform: generally, a human language description which unambiguously relates the inputs of a mechanism to the outputs
mircea_popescu: asciilifeform let's go into a lengthy sidepoint. can you define "specification" for my benefit ? strangely enough the prb tards think some things about what a specification is that diverge.
mircea_popescu: speaking of which, i must say this has been by far the most serious, deep and far reaching argument tmsr yet produced, i sit and marvel at the wonder, all my resources tapped taut and for the first time in many years insufficient to peer through the gloom.
mircea_popescu: there's some problems with the concept of "specification" also that i don't have clear in my mind ☟︎
mircea_popescu: only in given context. which is the problem.
asciilifeform: software is the one animal that ~can~ be perfect.
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.
a111: Logged on 2016-06-14 13:12 mircea_popescu: how do you put in "all the parts that are needed by ALL future users" but "no parts not needed by ANY future user" ?
asciilifeform: http://btcbase.org/log/2016-06-14#1482593 << this is called orthogonalization. and is a thing. even if lazy bastards never do it and consequently mircea_popescu has never seen it. ☝︎
mircea_popescu: asciilifeform i suspect this may be a case where your conscientious intelligence is moreover harmful in the very limited and passagery sense that it took you far enough down a blind alley to make digging out the proper route seem expensive and painful.
asciilifeform: i'm with mircea_popescu on this one ^ .
mircea_popescu: i do not wish my os to contain as much as a fucking variable declared i don't use. not one.
asciilifeform: this is something that always annoyed me, that folks write blobs that later have to be cut into parts.
mircea_popescu: how do you put in "all the parts that are needed by ALL future users" but "no parts not needed by ANY future user" ? ☟︎
mircea_popescu: at the very least any use will only want parts of it.
mircea_popescu: true static library is really the complete story : ascii's ffz + the various re-implementations of ffz in projects x y and z.
asciilifeform: there is no 'in the future'
asciilifeform: mircea_popescu: with static library that is NOT a thing
mircea_popescu: "open source" alleviates this like an emergency valve does ; but why the fuck have design processes which create items which rely on emergency valve already. fix the leaks.
asciilifeform: a fella who won't set foot on airplane has the luxury of 'i won't fly unless i built the thing'.
mircea_popescu: asciilifeform the fundamental problem with the "library" thing is that you are asked to guess what i might wish to do in the future. this is wrong, and unfixable.
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.
mircea_popescu: my shamelessly tall statement here being that, "library is the bad thing", outright.
asciilifeform: which is to say, a fairly heavy thing, that mircea_popescu is likely to use in his creations without reading.
mircea_popescu: which means there isn't "the os" anymore.
mircea_popescu: the deep stupidity involved should be directly apparent, but in any case - the system as proposed violates the proper flow of entropy, and as such MAY NOT HAVE ANY MERITS.
mircea_popescu: this idiocy is not only how computing "works" today, but it is also how a good "marxist leninist maoist" party cadre is expected to treat the inept shit they use : he's to import marx.library exactly like you're "expected" to import iosys.blabla
mircea_popescu: meanwhile, the way this continuum is handled in all failed human endeavours (computing among them, with such prideful items as "social science" and so on) is for "all possible uses" of a concept to be "dreamed up" and "packaged" in a "conceptual library" which is then to be used verbatim.
mircea_popescu: there obviously exists a continuum between abstraction and implementation. the way this continuum is handled in ~all (and absolutely all) successful human endeavours is, that a concept is clarified AS A CONCEPT ; and then that concept is applied to situations as an application. like the war, roman arch, et all.
a111: Logged on 2016-06-14 05:31 phf: well, mp already pointed at this with his roman arch example
mircea_popescu: http://btcbase.org/log/2016-06-14#1482521 << incidentally, i think this discussion unearthed another sacred idol of computing stupidity, deeply buried. allow me to go into some detail : ☝︎
a111: Logged on 2016-06-14 05:22 trinque: using openssl as a symbol, to the degree that your program relies on one, you cannot be said to have written any particular program at all
mircea_popescu: http://btcbase.org/log/2016-06-14#1482510 << whether you can be said to have "written" it, in the manner of genre fiction, is even a separate matter from "having written it" in the manner of code, which means you control it, which is a superset of you understand it completely, which has really little to do with "here's a string i dreamed up now publish it and clal it a book". ☝︎
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.
mircea_popescu: http://btcbase.org/log/2016-06-14#1482503 << it violates mine outright, so much so that on the first pass i ~ignored it. i hadn't at the time it's meant seriously, hard to tell what is a minor point and what a major point until discussion actually ends up on them. ☝︎
mircea_popescu: hence the whole "because i can". it's a misnomer : "because it can be done" is proper, the i has no business in there. it'd like to, but that's neither here nor there.
mircea_popescu: seful to us". it's not something it set out to do.
a111: Logged on 2016-06-14 04:55 trinque: every pit of ignorance on earth sits behind some tidy word beyond which "it's someone else's problem"
mircea_popescu: http://btcbase.org/log/2016-06-14#1482493 << word. really, "labour division" is harmful in the same manner jwzism is harmful, if practiced in the manner jwzism is practiced. the criteria for cleavage MUST BE "can these things be cleaved" ; it CAN NOT BE "would i like these things apart". it is and has to remain about the things, not about the people. and in this sense "engineering serves mankind" in the same way "the sun is u ☝︎
shinohai: ;;later tell BingoBoingo http://ix.io/SAs
shinohai: http://archive.is/xIxDz <<< ETH in the "press"
trinque: thus fuck your hyperlinks; give me the whole thing in one buffer
trinque: someone thinking of a specific problem rather than *the whole problem* sees it from the perspective of maximizing clarity of his own particular domain
trinque: asciilifeform thinking of it from the perspective of "mind amplifier" says in order to represent as much thought as possible, gonna need hyperlinking
trinque: it's whether software is a matter of engineering or of thought.
trinque: fascinating; I have a condensation of the whole conversation now
trinque: with the risk that something about bridge failure may end up causing your building to collapse
trinque: the physical world does not have this confounding problem