asciilifeform: 'So, I have a question - why do we need such an OPEN technologies, that can be BLOCKED tomorrow? Today - it's me, but who knows what will happen tomorrow, and which countries or companies will decide to block their, so called open, tools that you use.'
asciilifeform: as with many idiocies, this one may be approaching 'parody event horizon' where the reality is not readily distinguishable from the spoof world
asciilifeform: i definitely recall he was 'advocating' for 'diversity' in petri dishes, in every lab!!!11!! in one post
asciilifeform: forget the source; evidently, books - do not exist
asciilifeform: they sure don't make lying sc4mz0rz like they used to.
asciilifeform: assuming there was any actual comparison
asciilifeform: decimation: plus an obligatory helping of os brain damage
asciilifeform: decimation: fragmentation & seek penalty on ancient mechanical drives ?
asciilifeform must have awakened in parallel universe
asciilifeform: disk readahead caches, etc. evidently never happened?
asciilifeform: 'Gavin's testing of 20MB blocks shows that loading (disk io) for these is 4x faster than 20 1MB blocks.' << did someone actually make this argument ?
asciilifeform: and here i was, thinking i'll have to hang for jaywalking
asciilifeform: 'Any more information on this? The fact that he is secretly building 10k nodes on a network with 7k active nodes and dropping is a concern in itself and makes me want to support Gavin's hardfork even more so.'
asciilifeform was never able to read the phorum for more than a few min. at a stretch
asciilifeform: so -that- was the 'run into the ground' thing
asciilifeform: even if for some peculiar reason it were not possible to reduce consumption, the thing ought to know when about to be killed - and shoot itself in the head with some decorum, rather than wait
asciilifeform: needs replacement std::allocator - proggy is not normally aware of own footprint
asciilifeform: ben_vulpes et al: happen to remember what block height was at the time 0.5.3 was current? if this is in the log, i have utterly failed to find it
asciilifeform: ^ also happens to explain the memory thing
asciilifeform: not in the experimental 'orphanage burner' build
asciilifeform: hanbot: figure in question is ram footprint
asciilifeform knows how/why but still bewildered that no one has at any point seen it fit to bolt on basic sanity
asciilifeform: who the hell writes a program as hungry as this, that is entirely unaware of its own resource consumption and lacks any feedback mechanism ?
asciilifeform: this would require replacement of allocator (as suggested in thread from 2 days ago)