log☇︎
14 entries in 0.427s
ben_vulpes: pete_dushenski: i don't think anyone's using kelvin versioning on trb
asciilifeform: kelvin versioning is for proggy which ~solves~ well-defined problem, yes. it is to signal intent to converge, with exponentially smaller (in practice also ~rarer~) increments on eternal perfection.
assbot: Logged on 01-10-2015 10:20:06; mircea_popescu: more importantly : if kelvin versioning is not useful for diana's bot, on what exactly does the expectation that kelvin versioning is useful at all rest ?
mircea_popescu: more importantly : if kelvin versioning is not useful for diana's bot, on what exactly does the expectation that kelvin versioning is useful at all rest ? ☟︎
mircea_popescu: how would kelvin versioning work for diana's bot ?
asciilifeform: ;;later tell mod6 ~Kelvin~ versioning
asciilifeform: '...so nodes running an older protocol version will be skipped.' << phoundation's answer to us, yes. anyone contemplating kelvin versioning again ? why should enemy have this much of an easy time with rejecting our nodes?
asciilifeform likes kelvin versioning
undata: asciilifeform: were we not talking about the kelvin way of versioning code?
assbot: 3 results for 'kelvin versioning' : http://search.bitcoin-assets.com/?q=kelvin+versioning
asciilifeform: !s kelvin versioning
asciilifeform: on anything, hell, univac. kelvin versioning doesn't mean you will never throw the whole thing away. just experesses the concept that code must cool down to pefect crystalline form, rather than accumulating turdacles.
asciilifeform: i confess - i actually like moldy's 'kelvin versioning.'
asciilifeform: ;;google kelvin versioning