Hide Idle (>14 d.) Chans


← 2021-10-25 | 2021-10-27 →
verisimilitude: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-21#1061624 There's no reason to adhere to that stupid convention, cgra. I use one hundred columns as my limit, and it's just as reasonable as eighty, I'd argue more, since I avoid being so constrained for space.
dulapbot: Logged on 2021-10-21 13:17:46 cgra: noob question inbound...: why should a software author adhere to 80 columns?
signpost: it's just a relic of old terminal widths.
signpost: it's one of those things where most people require a rule to stay sane, where others can use their judgment.
signpost: there are plenty of cases where breaking a line to obey the rule makes the code harder to grok.
signpost: asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird.
signpost notes that it's a little over year and a half since #t was shuttered, and he's shifting life to focus on bitcoin and related work.
signpost: on the timescale of republics, I don't think that's such a bad score.
signpost: pity the bottle swallowed the old man, then the sea swallowed the bottle, but it doesn't change anything for me.
signpost will get back to publishing interesting items before long.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << indeed pascalesque, was 1 of the initial appeals for asciilifeform
dulapbot: Logged on 2021-10-26 09:48:01 signpost: asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird.
signpost: way less cognitive load than "what's this fucking bracket paired with again?"
asciilifeform: signpost: the design objectives were baked around 'coad must be readable or we might lose a space battleship' and it shows imho
signpost: indeed, clarity to reader as well as compiler
signpost: I will probably take some time before being useful in this language, but seems worth the time.
asciilifeform: signpost: imho ffa is the closest thing existing atm to a clean ada intro course
asciilifeform recommends, lol
signpost: major reason I want to grok ada.
asciilifeform: signpost: must note though that ffa doesn't cover the 'gnarly'/cppesque features of the language, deliberately avoids. (and they aint entirely useless, e.g. nqb makes use of some, chiefly streams)
signpost probably wants streams for the xor-a-tron too, but makes sense to stay simple for ffa.
asciilifeform: streams in nqb on account of the gnarly tcpism of the bitcoin wire protocol, with its various 'variable-length' turds
asciilifeform: (and in general they're the correct abstraction when a format contains variably-long crapola and no one has any idea what before parser eats it)
asciilifeform: imho one oughtn't perpetrate these tho, when has a choice.
signpost will have to sink into it to have a good opinion on whether to use.
asciilifeform as noted in 'trbi' threads, would've made e.g. fixed 1024byte tx, and 1024 of'em per block, or somesuch. but in trad bitcoin we have what we have.
asciilifeform: 'nqb' was actually about this -- attempt to represent traditional tx/blox in a maximally, as possible, 'trbi'-like form, for O(1) storage/retrieval.
signpost: in the case of onlinecodes, counterparty hucks you udp packets representing check blocks, and you know how much stuff you should receive before the original message is solvable.
asciilifeform: imho doesn't require a stream abstraction. but i expect will be clearer once you bake prototype
signpost has thought ring buffers might be appropriate.
signpost: oughta be able to alloc a suitable size right at the beginning, pop check blocks into it, then either write the solved message to a second array, or disk
asciilifeform: signpost: i'd expect the initial 'here's a warez' packet will have the final size & hash in it
asciilifeform: so can preallocate.
signpost: yep indeed
asciilifeform: ( preallocate with 'cryostat', naturally )
asciilifeform: really does take ~100% of the headache outta 'need megaturd in memory, for possible save to disk' etc
signpost: oooh yes, had forgotten.
asciilifeform wrote it chiefly for use w/ 'nqb'
signpost will review 100% of asciilifeform's ada material before setting off.
asciilifeform: 'cryostat' is simply a clean (imho) bolting of mmapism to gnat.
asciilifeform: is enabled by the a++ lang feature where can 'for Item'Address use GetAddress(Map);'
asciilifeform: in c world, this kinda thing is inevitably an ocean of pointerisms and pestilential typecasts errywhere
asciilifeform: whereas here, can avoid, and then use the map 100% as if it were an ordinary stack variable.
asciilifeform: saves to disk when goes outta scope, too.
asciilifeform: so in principle can take any ada proggy and make its state persistent, with coupla ln added.
asciilifeform: given as ada gives you full control over allocator, could even make the entire stack persist.
asciilifeform sadly not had chance to weld 'cryostat' to 'nqb', got into an unspeakably arduous commercial contract soon after publishing the former, and still mired in liquishit
dulapbot: Logged on 2021-10-25 19:50:06 billymg: asciilifeform: my fix for one bug created another. search results use span.highlight, which the div.highlight no longer targets. it should have both, like this
asciilifeform: !q uptime
dulapbot: asciilifeform: time since my last reconnect : 132d 11h 55m
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $62021.95
asciilifeform: !w poll
watchglass: Polling 17 nodes...
watchglass: 84.16.46.130:8333 : Could not connect!
watchglass: 185.85.38.54:8333 : Could not connect!
watchglass: 185.163.46.29:8333 : Could not connect!
watchglass: 205.134.172.27:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 (Operator: asciilifeform)
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706802
watchglass: 71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.118s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 (Operator: asciilifeform)
watchglass: 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.111s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
watchglass: 205.134.172.26:8333 : Alive: (0.129s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706802
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.143s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
watchglass: 208.94.240.42:8333 : Alive: (0.225s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
watchglass: 205.134.172.28:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706773 (Operator: whaack)
watchglass: 213.109.238.156:8333 : Alive: (0.332s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
signpost: cryostat seems like exactly the thing, looking forward.
watchglass: 143.202.160.10:8333 : Alive: (0.520s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
watchglass: 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.594s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802
watchglass: 176.9.59.199:8333 : (static.199.59.9.176.clients.your-server.de) Alive: (0.638s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=483140 (Operator: jurov)
watchglass: 54.38.94.63:8333 : Violated BTC Protocol: Bad header length!
watchglass: 192.151.158.26:8333 : Busy? (No answer in 100 sec.)
cgra: thanks asciilifeform, verisimilitude and signpost for 80 col comments. personally had already also developed a general feel of around 100-120 col being "most comfortable". now summarized in my own head that need 80-90 col only mostly if want to unconditionally support code on paper.
cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << i remember as a teen/kid (forgot year exactly) to prefer learning pascal over c/c++, and kept sticking to pascal and thinking why is c++ so damn weird, like 'std::out << "printed text"'
dulapbot: Logged on 2021-10-26 09:48:01 signpost: asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061936 << i do the paper thing for just about any nontrivial item (i.e. that takes >1d of thought) so muchly prefer 80.
dulapbot: Logged on 2021-10-26 12:34:24 cgra: thanks asciilifeform, verisimilitude and signpost for 80 col comments. personally had already also developed a general feel of around 100-120 col being "most comfortable". now summarized in my own head that need 80-90 col only mostly if want to unconditionally support code on paper.
asciilifeform: (and fits on vertical display in reasonably large letters w/out horiz. scrolling or wrap)
asciilifeform: wrapping fucks up indentation
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061937 << 'syntactic sugar causes cancer of the semicolon'(tm)(r)
dulapbot: Logged on 2021-10-26 12:44:23 cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << i remember as a teen/kid (forgot year exactly) to prefer learning pascal over c/c++, and kept sticking to pascal and thinking why is c++ so damn weird, like 'std::out << "printed text"'
asciilifeform working w/ commercial client who doesn't do 80col (or any limit at all) and the coad looks like shit on paper
cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061941 << how many columns (in reasonably large letter size) does your typical vertical display have?
dulapbot: Logged on 2021-10-26 12:47:09 asciilifeform: (and fits on vertical display in reasonably large letters w/out horiz. scrolling or wrap)
asciilifeform: cgra: 80, lol
← 2021-10-25 | 2021-10-27 →