5300+ entries in 0.298s
mircea_popescu:
phf and the effect is especially negative when the girl overdoes the make-up lines, as some girls do.
a111: Logged on 2017-01-07 18:15
phf:
http://btcbase.org/log/2017-01-07#1598258 << you know those guys that periodically stop by lisper venues, and they don't really program, but they want to use LISP to build an AI, because metacircularity of code is data is giving them mystical visions..?
mircea_popescu: (i would like to thank the academy, the harem sluts, and
phf / ben_vulpes discussions for inspiring me to come this far!)
mircea_popescu:
phf every whorish ditz i ever knew has a linkedin account.
a111: Logged on 2017-01-05 21:13
phf: it's safe to save 66.35.48.19 for glyf.org, it's been the same ip for the past 10 years or so. in fact, assuming this is not some weird overflow issue, today is a birthday on glyf.org machine. 2048 days uptime
a111: Logged on 2017-01-05 19:34 mircea_popescu: yo
phf ben_vulpes: asciilifeform: no, it's not
phf's, it's magit and i think ediff
adlai: not a full solution, but i do recall
phf mentioning some animation software driven by sexps
ben_vulpes: asciilifeform: i've been working on
phf's recommendations of late
ben_vulpes: imma finish this
phf-inspired patch and fix the miner
ben_vulpes:
phf: i think this is pretty neat, have wondered about your x-referencer etc
mircea_popescu:
phf yes, but a fine approach to answering "what is the basis of alf's value as an engineer" is pointing out that he runs phuctor on the phuctor box, which fails to cost 5k/mo.
jurov:
phf no mircea imagines he can order c machine "read me this without any locking, but it must be in some class or!"
davout:
phf: you're saying postgresql doesn't have a "read uncommitted" transaction isolation level like innodb?
mircea_popescu:
phf here's the problem : moder(field) consists of take field, redefine it in a practically useless but superficially persuasive way, then bad_words() to whoever dares ask if your "field" solves any important questions in the field. because of course it doesn't, MIT is the premier institution in science(*) and technology(*) in the werld.
☟︎ mircea_popescu:
phf i am saying that if you imagine the user can be relied on to "know where the locks are and read around them" then you are therefore necessarily saying "locks are useless - user can always know what he wanted locked and simply not write there hurr"
mircea_popescu:
phf think for a second : the whole FUCKING POINT of a semaphore, of any kind, is that user can't know what the other item involved is doing. if they could know, they wouldn't "avoid the locks", they'd avoid the bad write outright.
davout:
phf: iirc mysql's innodb lets you choose your isolation level per transaction
a111: Logged on 2016-12-30 05:40
phf: so if you were to produce a patch with a/old-veh.lisp and b/veh.lisp. existing vtrons will happily press it, though it's a total clusterfuck
a111: Logged on 2016-12-30 05:22
phf: i think it treats one of the names as canonical
ben_vulpes:
phf: when it works, it outputs the list of patched files
ben_vulpes: wait
phf hang on no i don't think i'm going to do the largest common, i think i'm just going to use the output of patch to figure out what was actually patched
ben_vulpes:
phf: when i crack my v again in the morrow, i'm going to implement hash-checking against longest common directory tree
a111: Logged on 2016-06-20 04:23
phf: which is handy if you're using something else to produce the patch, or if you need to use a non-trivial diff command. for example i sometimes need to exclude files from diffing, so a command might look like diff -x foo -x bar -x qux -ruN a b | grep -v '^Binary files ' | vdiff > foo.vpatch
ben_vulpes:
phf: i actually can't get patch c/old.lisp and d/veh.lisp to apply derp.vpatch
ben_vulpes:
phf: patch will apply something cleanly with mismatched depths, won't it?
trinque:
phf: when I brought to you "whence the disjunction between the practical and theoretical sides of subj" your output was "OP == faggot"
mircea_popescu:
phf for my own curiosity, does anything in the rest of your life piss you off as much in aggregate as one session with these assholes ?
a111: Logged on 2016-12-30 00:04
phf: newline is not a non-printable
mircea_popescu:
phf i guess we will sooner or later have to actually formulate the patch format yeah.
a111: Logged on 2016-12-28 02:39
phf:
http://btcbase.org/patches/hashes_and_errors#L118 you don't really want to do this. you're subseq'ing there to strip the a/ b/ but that's not at all a guarantee! i have a vpatch with `diff -ib -ruN /Users/pf/cmucl20d-build/src/hemlock/abbrev.lisp src/abbrev.lisp` in it for example. at the very least you want to abstract it away into its own function. that would correctly operate on a hashed-path datastructure.
ben_vulpes:
phf: moreover i'm too ferklempt over how the thing's changed since 10.2 to want much to do with it anymore
ben_vulpes:
phf: i only used windows as a wee one in school labs and a mildly less wee one in cad labs, so no idea re administration haxery
mod6:
phf: ok, see, there is a hack i could have put in, instead. where i just ensure that my root is named like /genesis/. But what if someguy calls his root, 1000 years from now, xyz.vpatch.
mircea_popescu: anyway,
phf 's notion of "recourse" is a lot more important than directly obvious in context ; it's a direct restatement of the "opposable" concept used in discussing deedbot payment design, and altogetgher the trestlework of sanity in operations.
Framedragger:
phf: fair. with regards to chatting up it was more to do with me not being involved with tor anymore; but even that particular still stands, so yes fair
mircea_popescu:
phf the clearing of head is a slow and painful, mostly private process. now he has a definite reference point to come back to later at least.
a111: Logged on 2016-12-28 02:17
phf: there's not much discipline on unix with stderr/stdout. particularly gpg seems cavalier with it. so i wouldn't even bother with error/output separation. i'd make it always return a single value, string that's combined stdout/stderr, and fail when status code is not equal to zero. maybe add a key argument, that splits them if need be, but only once there's need.
a111: Logged on 2016-12-28 02:39
phf:
http://btcbase.org/patches/hashes_and_errors#L118 you don't really want to do this. you're subseq'ing there to strip the a/ b/ but that's not at all a guarantee! i have a vpatch with `diff -ib -ruN /Users/pf/cmucl20d-build/src/hemlock/abbrev.lisp src/abbrev.lisp` in it for example. at the very least you want to abstract it away into its own function. that would correctly operate on a hashed-path datastructure.
a111: Logged on 2016-12-28 01:56
phf: i'd write it as (cmd &optional args &key input), because you always have to provide cmd (where's right now you can write (run) and the compiler won't catch it), more often than not you have to provide args and sometimes you have to provide input
a111: Logged on 2016-12-28 02:41
phf: i'm going to stop wall of texting the log though
a111: Logged on 2016-12-28 02:34
phf: heh, this is straight up rubyism
http://btcbase.org/patches/veh-genesis#L145. it would've been much cheaper to (defstruct hashed-path path hash) and so that later you don't have to poor man datastructure by (gethash 'path ...) (gethash 'hash ...) all over the place
a111: Logged on 2016-12-28 02:25
phf: also in the same handler-bind you're losing a branch. if there's an error, but it's not "BAD signature", then the whole verify silently succeeds. you probably want to (error c) in the else branch to rethrow whatever
a111: Logged on 2016-12-28 02:17
phf: there's not much discipline on unix with stderr/stdout. particularly gpg seems cavalier with it. so i wouldn't even bother with error/output separation. i'd make it always return a single value, string that's combined stdout/stderr, and fail when status code is not equal to zero. maybe add a key argument, that splits them if need be, but only once there's need.
a111: Logged on 2016-12-28 01:58
phf: also as a rule you don't really want to let string output streams escape their scope. they don't have standard type (one cmucl it's lisp::string-output-stream for example), so you can't test for it, and for all intents and purposes they act as incomplete builders: you can't do anything with them except get their value, so why not get value there and then?
a111: Logged on 2016-12-28 01:56
phf: i'd write it as (cmd &optional args &key input), because you always have to provide cmd (where's right now you can write (run) and the compiler won't catch it), more often than not you have to provide args and sometimes you have to provide input