19800+ entries in 0.077s
adlai:
mircea_popescu: nah, back in middle school mrs whatsit told me not to forget those because they help to end e sentence, yet mene hesn't even begen yet!
a111: Logged on 2017-01-02 22:10 hanbot: <
mircea_popescu> but i am well and truly at a loss, who owns it ? no idea. maybe lobbes ? i somehow du nthink it was mike_c- << i'm pretty sure it was his, yeah.
a111: Logged on 2016-12-24 17:45 asciilifeform: this 'works' is a pestilence and is largely why clueful greybeards from the meat world , e.g.,
mircea_popescu , unzip and piss on programmers simply for sport
a111: Logged on 2017-01-02 21:40
mircea_popescu: if the same archbishop inquires as to why i poured cement the way i did i can answer without ado.
a111: Logged on 2017-01-02 21:36
mircea_popescu: what do you answer when they ask "what do {} do" ?
a111: Logged on 2017-01-02 21:29
mircea_popescu: "oh that's what those do." "yes." "but why." "nevermind"
a111: Logged on 2017-01-02 21:22
mircea_popescu: 90% of my audible output was "your question can not be answered in that general form". tears were shed, of rage and frustration. towards the third day i recited from the molieben of st naggum, the part where he says c makes people lie, and there was THANK YOU! GOOD GOD!
hanbot: <
mircea_popescu> but i am well and truly at a loss, who owns it ? no idea. maybe lobbes ? i somehow du nthink it was mike_c- << i'm pretty sure it was his, yeah.
☟︎ diana_coman:
mircea_popescu, ftr I saw and even experienced this sort of trouble but unrelated to C++ as such - related to *programming* in itself really, regardless of language
diana_coman:
mircea_popescu, I don't think I basically get enough of what it was that was going on there to comment much further
a111: Logged on 2017-01-02 18:21
mircea_popescu: rather than everyone just using the cache like it were a gpu
trinque:
mircea_popescu: link works now
jhvh1:
mircea_popescu: Bitfinex BTCUSD ticker | Best bid: 999.07, Best ask: 999.25, Bid-ask spread: 0.18000, Last trade: 999.0, 24 hour volume: 13737.10782109, 24 hour low: 961.26, 24 hour high: 1006.5, 24 hour vwap: None
trinque:
mircea_popescu: I've wondered whether it is apt to call these human aggregates gods, in that the term was a passable label for distributed-world-model running among nodes of a wot
shinohai:
mircea_popescu: You can unset those with /umode -w
mircea_popescu in #freenode ; <
mircea_popescu> christel is there some manner to opt out of the cutesy/pointless global notices ? or otherwise out of these global notices altogether ?
ben_vulpes:
mircea_popescu: buying drinks is one thing, girl soaking everything in sight less common
a111: Logged on 2016-12-30 20:45
mircea_popescu: none of this stuff CAN be fixed.
davout:
mircea_popescu: iirc there was one locktime thing that was there from day 1
mats:
mircea_popescu: no, i wish
davout:
mircea_popescu: yeah, i meant it as a separate, user-initiated step
ben_vulpes:
mircea_popescu: we're cramming a year+ of wallet into davout's head now that he's paying attention again
davout:
mircea_popescu: ok, "forbid-insane-fee" then
phf:
mircea_popescu: rds is amazon's hosted relational database solution(tm) which is a postgresql on a unixbox
jurov:
mircea_popescu: yes, but most of www can live with crashing database (even innocent reading can cause sigsegv, sadly)
a111: Logged on 2016-12-30 17:56
mircea_popescu: jurov no ; but i am fine with wwwtron ocasionally reading a field that has meanwhile been updated, and giving old, of an unspecified age but less than x time.
a111: Logged on 2016-12-30 17:49 jurov:
mircea_popescu: you would trade speed for occassionally getting garbage when you call read()?
a111: Logged on 2016-12-30 17:29
mircea_popescu: exactly how the statements {"do not allow anyone else to write here until i say" ; "let anyone read anything at any time"} amount to an "unsolved problem in cs" ? and wtf cs is this we speak of, sounds more like chewinggum-science.
jurov:
mircea_popescu: this is the problem with c machine, that everythign is pointer, and without preemptive locking, you can't distinguish your pointer points to merely stale data vs. garbage
jurov:
mircea_popescu: in this case asciilifeform categorically claimed he decided to have consistency, or are you deciding otherwise?
jurov:
mircea_popescu: you would trade speed for occassionally getting garbage when you call read()?
☟︎ phf:
mircea_popescu: that's not quite what i'm saying.
davout:
mircea_popescu: seems to me like it would reduce to 'moving the problem'
phf:
mircea_popescu: i'm not quite groking what the bad write is. are you saying that instead of intermingling writes and reads, you should batch them, and not write while you're reading?
phf:
mircea_popescu: yes, ~having to deal with locks~ happens past the limit of db designer's competence
phf:
mircea_popescu: sop outside of mysql world. dirty read is considered a liability, so whole point of db systems design is to ensure that you don't hit locks when you shouldn't.
a111: Logged on 2016-12-30 16:28
mircea_popescu: but he might be interested to hear about it.
Framedragger:
mircea_popescu: because you could tell postgres to flush rows (forcing all caching layers) every 100 rows, not every 1 row as currently specified
Framedragger:
mircea_popescu: consider a scenario in which you knew how much data you could lose ("up to 100 last rows"), and you could check if you lost any (last row id == last-id-processed.txt ? false : true). that being said, this way things become more wibbly-wobbly, so probably fuck that. :(
Framedragger:
mircea_popescu: it's dark here in the northern hemisphere, god it's deperessing :( mornin'..