asciilifeform: then you will have a jewel in your toolbox that you can use 20 years from now
asciilifeform: http://log.bitcoin-assets.com/?date=02-08-2015#1222073 << this is seriously, deeply 'un-lispy' code. it explicitly reads fields!!! what you oughta do is define the 'message' structure in the most minimal way you can think of, and then write a routine that snarfs any structure defined that way, whatever it may be.☝︎
asciilifeform: reminiscent of what mircea_popescu suggested, but with moar duct tape and chicken wire
asciilifeform: punkman: the linked page is connected to a live pool. and demands password (presumably subscriptions are sold?)
asciilifeform: can give the 'atoms' electrostatic-style charge, so they repel, and the bonds - 'strain', so they contract☟︎
asciilifeform: except there is no reason to make it a clicking and dragging game
asciilifeform: trinque: the 'springy' thing is quite like the molecular strain sims i've used
asciilifeform: the above observation is not a criticism of solrodar's work, but of the catastrophically inadequate existing tooling
asciilifeform: this conveys ~zero~ useful information. in particular, the fact that 'CNode :: PushVersion' is a deadcode island is no longer visually apparent.
asciilifeform: you will see things like: 'CNode :: PushVersion' is connected! to whom?? to 'CNode :: CNode'.
asciilifeform: and, after you do this, aside from the nightmare of intersecting lines and bubbles light-years away from their ~only~ antecedent, etc,
asciilifeform: gotta be viewed in a graphical www browser, so you can search
asciilifeform: incidentally, it is worthless if flattened into a bitmap
asciilifeform: the place i'm trying to go with this is: dead code ought not be in The Book, except - in the one and only case where it pre-dates gavin et al, it could be shoved into an appendix
asciilifeform: (wallet, for instance, would look entirely 'dead' on a gcov run where such was not used)
asciilifeform: trinque: gcov is useful but doesn't prove code to be alive or dead, can only suggest
asciilifeform used grep to answer the question, unambiguous 'no'
asciilifeform: well i just gave an example. can you tell from that picture whether it is theoretically possible for the 'subscription' routines to be called?
asciilifeform: though, strangely enough, the best-performing (e.g., fewest 'black hole' issues) node in my fleet thus far has been 'zoolag', which is sitting under my desk, on residential fiber
asciilifeform: mircea_popescu: fortunately there is wildlife that lives on usg-free net, whose turds one can follow to find the forest. i speak, of course, of crapware artists and sp4mz0rz
asciilifeform: <mircea_popescu> obviously c will compile for anything. but not by itself! << my point was that i put a complete kit in there. that will build x86_64 on whatever you like, x86-32, cray, pdp11.
asciilifeform: it also ~never~ happens between directly-connected nodes on my lan, for example.☟︎
asciilifeform: it is precisely as if someone were snipping out just the packets with useful payload, while leaving enough in place to leave the connection open.
asciilifeform: decimation: i 'wiresharked' many hours of this.
asciilifeform: 'The cash was seized, pending an inquiry that was hampered by the individual’s initial refusal to provide any information about its source. Once the investigation was complete and no basis for forfeiting the cash had been established, it was handed back.' << ahahahaha
asciilifeform: mircea_popescu: thing is, their scam skillz are honed for a certain kind of largely-ritualized competition. like the antlers of ruminants. for actual combat - not so much
asciilifeform: the tighter a tournament market, in usa, the more this is selected for.
asciilifeform: that's what 'go-getter type' has ~always meant in usa~. a fella willing to lie, defraud, with straight face
asciilifeform: incidentally, the american style of schooling strongly selects for this
