asciilifeform: this presupposes that the task can be cut.
asciilifeform: maybe i misunderstood the idea ? what was meant ?
asciilifeform: i do not need 'stable boy' for anything. there is no conceivable room, imho, for any such thing in any of my systems.
asciilifeform: imho to even suggest such a thing, betrays a very serious misunderstanding of the concept. dumb humans are in every respect an inferior version of the machine. the only thing more agonizing than programming comp, is programming dumb humans.☟︎
asciilifeform: but meanwhile i also must address the 'stable boy' thing
asciilifeform: the performance wins described in this thread by Framedragger and trinque can only come at the cost of 1) massive increase in complexity, and in particularly state 2) loss of immediate linkability of freshly pasted keys.
asciilifeform: the apparent willingness of, e.g., Framedragger , to introduce petro-cheese is quite depressing
asciilifeform: ( to dispense, for instance, with immediate linkability )
asciilifeform: given that i found that various otherwise reasonable people are willing to make all kinds of compromises
asciilifeform: at one point i thought that giving it to other folx could be a reasonable thing. now i ~definitely~ do not
asciilifeform: and if you think rewriting 600 ln. of python is painful -- try rewriting 60,000. which is what is being proposed : to give asciilifeform 60,000 lines to later inevitably rewrite.
asciilifeform: or the cost of getting a 2nd box with five-nines uptime.
asciilifeform: this is not even to mention the complexity cost.
asciilifeform: (immediate linkability of newly-pasted-in gpg key.)
asciilifeform: while retaining what i see as the non-negotiable features.
asciilifeform: i don't presently see them as cleanly cuttable apart
asciilifeform: trinque: sorta what Framedragger was discussing, neh
asciilifeform: understand, if i paste a gpg key into phuctor, and cannot then ~immediately~ link to it in-chan -- phuctor is broken!!☟︎
asciilifeform: you are STILL stuck writing new submissions to the front.
asciilifeform: having two databases sounds superficially like a great thing, until you realize that the read-write thing applies just the same to the 'front' one as it does to the existing single.
asciilifeform: asciilifeform specifically does not do this.
asciilifeform: i am quite aware that 'software industry' today consists of multiple layers of shit sandwitch, each and every one of which consisted of 'great optimization! all you gotta do is add this 5000 lines of code and 40 layer tree of state that gotta be kept consistent'
asciilifeform: see the userland fs thread, with the rebalances.
asciilifeform: it is -- quite obviously -- doing work that dun need doing. behind the curtain. 'for your own good.'
asciilifeform: the disk can push 150 MB/sec. if the db cannot do 150 MB/sec, it is retarded and must burn.
asciilifeform: and knows how to read while writing without stepping on own shoelaces.
asciilifeform: does he IMMEDIATELY get a bookmarkable link based on the key's hash ? that he can come back to next hour, next day, next decade ? if so, how ??☟︎
asciilifeform: what happens when a user submits a gpg key ?
asciilifeform: theoretically this can be done on one box. but -- for my enlightenment, Framedragger , describe to me :
asciilifeform: understand, Framedragger, it is 600 lines, now.
asciilifeform: Framedragger: you're talking about replication. replication, generally speaking, doesn't work. certainly not on posgres or any other free db, and certainly not without titanic sweat and inevitable increases in attack surface.
