a111: Logged on 2018-07-05 18:02 phf: gentoo out of the box turned out to have all kinds of interesting surprises (i haven't ran gentoo in years, so it was interesting to see the holes through which the darkness comes). like the foo-9999999.ebuilds that just pull from the mystery github repos without any kind of checksumming

a111: Logged on 2018-06-30 13:45 phf: https://queue.acm.org/detail.cfm?id=3212479 "C Is Not a Low-level Language: Your computer is not a fast PDP-11."

a111: Logged on 2018-06-18 23:08 trinque: phf, Mocky, and others waiting on cuntoo, the genesis.vpatch which contains only the ebuilds necessary for a minimal system is about 4mb.

a111: Logged on 2018-07-03 19:22 phf: http://btcbase.org/log/2018-07-03#1831431 << looks like it indeed was a loose screw. reassembling the thing fixed the issue

a111: Logged on 2018-07-02 22:34 phf: http://btcbase.org/log/2018-07-02#1831410 << his work in progress parser doesn't handle end of file, so as of right now the error is normal

a111: Logged on 2018-07-02 17:24 mircea_popescu: i'm looking for roads into the os. could be from phf's emacs, could be from spyked 's lisp, could be from your arms, could be from whatever the fuck ends up working.

a111: Logged on 2018-06-30 15:12 phf: asciilifeform: long work week?

a111: Logged on 2018-06-29 03:26 phf: https://hope.net//schedule.html for expert entomologists

a111: Logged on 2018-06-27 18:18 phf: vtools are already pre-heathened, support apple and freebsd

a111: Logged on 2018-06-26 17:45 phf: trinque: one reason i didn't include patch name in the manifest is because patch name becomes a promise, unless you enforce it by tooling. i didn't want to go that way, but since current standard manifest does include patch name, than perhaps V ought to check the manifest against the patchset. relatedly fully manifest-based v doesn't even need graph tooling, can presumably press according to manifest's chain.

a111: Logged on 2018-06-15 17:26 phf: http://btcbase.org/log/2018-06-15#1825631 << updated, but it's a novel way of using manifest though: normally it requires a regrind where manifest is built up as you go, so the press order is enforced through graph. right now your manifest gives a press order, that's not enforced by anything

a111: Logged on 2018-06-23 20:39 phf: "beware of dog"? seems unlikely though..

a111: Logged on 2018-05-31 21:40 phf: i remember seeing the archive.org version of the relevant page, but i think the correspond tar.gz was not in archive, and i gave up tryin to track it down

a111: Logged on 2018-06-22 03:42 phf: well for one, they all talk like the doms they've seen on tv, "i bore me now" "run along little pet" i mean what's next "beg, worm"?

a111: Logged on 2018-06-22 02:49 phf: http://btcbase.org/log/2018-06-21#1828378 << distinctions like that are often subtle and a matter of taste, but as long as the overal approach is informed now might be a good time to paste what you have.

a111: Logged on 2018-06-22 02:49 phf: http://btcbase.org/log/2018-06-21#1828378 << distinctions like that are often subtle and a matter of taste, but as long as the overal approach is informed now might be a good time to paste what you have.

a111: Logged on 2018-06-21 16:13 mircea_popescu: phf there were takers, mod6 working on rawtx recall ?

a111: Logged on 2017-11-20 12:23 spyked: http://btcbase.org/log/2017-11-14#1738140 <-- ftr, I am following phf's initial advice re. reading lisp in small pieces; this, along with kogge's book. but at snail's pace (code easier to write than read)

a111: Logged on 2017-11-20 12:19 spyked: http://btcbase.org/log/2017-11-14#1737923 <-- also, spyked's adalisp is missing more fundamental things, such as closures. it's an early prototype, barely usable, but > 0. interning is of course considered, but not added yet. anyway, phf, consider the following point: built-in symbols (car, cons, etc.) still have to point *somewhere*, and that somewhere must not be addressed in a C-machine style! symbols should point to Lisp memory (via

a111: Logged on 2017-10-08 14:06 phf: spyked: r5rs and tinyscheme are not the right places to start on the other, non-ada end, i'd recommend looking at lisp in small pieces. you can tease out the theory out of tinyscheme, but it's definitely easier not to get bogged on accidentals if you start from theory

a111: Logged on 2018-06-21 16:29 asciilifeform: http://btcbase.org/log/2018-06-21#1828076 << phf in retrospect tinyscheme plugin was an ill-conceived thing. such item really calls for a troo adatronic scheme thing.

a111: Logged on 2018-06-21 01:29 phf: much hairy, unix.lisp, runtime, sbcl's new approach of doing every single bit of ffi by writing C function wrappers first

a111: Logged on 2018-06-21 16:08 phf: http://btcbase.org/log/2018-06-21#1828005 << the closest we got to a replacement i believe was asciilifeform's shiva, i.e. a tinyscheme embedded into trb runtime. it was suggested as a useful exercise for novices to attempt to expose existing, useful rpc function using it, but there were no takers. at some point the idea of using shiva in prod also went away, because tinyscheme is not necessarily production ready (primarily because of C-ism issues). as

a111: Logged on 2018-06-21 01:22 phf: typically hashtables stay stable over invocations of same code, i wonder where randomness is even coming from

a111: Logged on 2018-06-19 18:08 phf: asciilifeform: well, it's been ported, but i've no idea how, last time i looked at it was pre-rework and i couldn't figure it out. trinque just said that the musl version of emacs he has is 24.5, so presumably that works

a111: Logged on 2016-04-22 00:36 asciilifeform: phf: the emacs tumour (see logz, the 'flycheck' thread) is what really blew my mind