log☇︎
39600+ entries in 0.019s
asciilifeform: ^ the Right Thing.
pehbot: asciilifeform: EGGOG: FATAL: Tick: 32 IP: 32 Symbol: '!' : Attempted movement to IP: 5 violates the Cutout!
pehbot: asciilifeform: EGGOG: FATAL: Tick: 59 IP: 11 Symbol: '!' : No Subroutines were defined prior to this position!
Mocky: BingoBoingo: once i get everything imported to my satisfaction on mockyhabeeb.com I'd like to cut over to mocky.org, so apache config I think
BingoBoingo: <Mocky> I'm going to finish moving my blog over to mpwp this week. I expect I'll need some pizarro assistance for go-live. Then Imma post remaining handful of Qatar posts, including video of my address to Doha derpchain gathering. << Let me know what you need
asciilifeform: i'ma leave the bot alive nao , for if anyone wants to play.
asciilifeform: ^ does Right Thing .
pehbot: asciilifeform: EGGOG: FATAL: Tick: 2 IP: 2 Symbol: ';' : Currently in a Loop state; but this Op exits a Subroutine !
pehbot: asciilifeform: EGGOG: FATAL: Tick: 24 IP: 13 Symbol: ',' : Currently in a Subroutine; but this Op exits a Loop state !
pehbot: asciilifeform: EGGOG: FATAL: Tick: 14 IP: 14 Symbol: ';' : Conditional Return in Sub: 'foo' is Prohibited! (Please check for unbalanced '{'.)'
Mocky: I think I get it but havn't used yet, other than a trb build from online that didn't require much thinking.
asciilifeform: imho v is the simplest, mechanically, versionatron ever baked. so i dun expect Mocky will have much of problem
asciilifeform: ( even tho it is about the ancient proof of concept vtron, with old-style hashes etc., re the basic mechanics it is still 100% correct )
asciilifeform: Mocky: the likbez by ben_vulpes is still imho the gold standard
Mocky: after that i'll have free hands looking for somthing to do
Mocky: I'm going to finish moving my blog over to mpwp this week. I expect I'll need some pizarro assistance for go-live. Then Imma post remaining handful of Qatar posts, including video of my address to Doha derpchain gathering. ☟︎
feedbot: http://bimbo.club/2019/03/philosophical-transactions-for-the-months-of-june-july-and-august-1715-part-i/ << Bimbo.Club -- Philosophical Transactions. For the months of June, July and August, 1715. - Part I.
asciilifeform: ( incidentally, 'can redefine cpu instructions in boot rom for custom kompyooting' dun require fpga etc. fancy modern tech, e.g. dec alpha had it )
asciilifeform: likewise, operator at least oughta have the ~option~ of 'all MULs take same # of cycles', even if no one wants this on server.
asciilifeform: the 'meta-sanity' arguably is that operator oughta be able to at least switch off the cache. ( you cannot, e.g., on x86, switch off l0 cache )
asciilifeform: ( to take simple example, you defo want cache on server, but it is absolutely lethal on ciphertron )
asciilifeform: theoretically what is 'sane' for machine to fiddle with proggies on, is not appropriate for server, or for ciphertron, etc
asciilifeform currently suspects that '1 sane comp for all problem domains' is a misapprehension of the problem, and that '1 for crypto, 1 for other things' is merely the beginning of it.
asciilifeform: if nuffin else, some of asciilifeform's demands re 'sane comp' are in architectural tension with others ( rather like to ask 'i want sword that cuts other swords, but isn't brittle' )
asciilifeform: ftr i do not have any notion that http://www.loper-os.org/?p=284 is 'last word on subj'
a111: Logged on 2019-03-26 21:18 diana_coman: if it's about wants, I can throw in that I want a sane computer already!
asciilifeform: http://btcbase.org/log/2019-03-26#1904962 << not to let this escape; i'd actually be quite interested to read diana_coman's own thoughts re what is a sane comp. ( asciilifeform wrote at great length re the subj, would also like to see where folx disagree / expand ) ☝︎
asciilifeform: but prolly cannot escape to have a glue for it, while we sit on irc , load www for various uses, etc
asciilifeform: rather than reasonable foundation for anyffin new
asciilifeform: asciilifeform sees tcp as a legacy tech, really
mircea_popescu: might tbe a better route, esp if it delivers a cheap way to a tcp-based republican web, to replace the www.
asciilifeform: i'll add that even a tcp skin wouldn't be entirely useless ( right nao the only way to write a wwwistic proggy in ada is to use adacorpse's 'gnatsockets' crock of shit ) ☟︎
asciilifeform: then can talk to mysql etc. just like trinque's cl proggy does
asciilifeform: shortest path to wrapper would be a http://www.loper-os.org/?p=2557 -style skin for unixsocketism.
mircea_popescu: can use mmap etc to fix the substance later.
mircea_popescu: no argument there ; also so far, let's just first get a wrapper.
asciilifeform: if sanely architected on sane abstration tower.
asciilifeform: but i also suspect that even 'all those things' dun actually require mil+ loc.
asciilifeform: having since '13 when 1st touched the subj, actually rftm'd, i'm not even prepared to say that 'who needs all those things'
a111: Logged on 2018-11-15 02:29 asciilifeform: phuctor ( and in particular, some of the 'heavier' / unusual pheatures, like search ) i baked specifically around postgres.
mircea_popescu: yes man, but trad dbs do a lot of things, including http://btcbase.org/log/2018-11-15#1872293 ; i can appreciate the "fuck this mn lines of c" argument, but this isn't the time to feather-macaroni just yet. ☝︎
asciilifeform: mircea_popescu: not at 'pen' stage , but prototyped, iirc i posted an example with trad btc tx.
asciilifeform: ( in the last iteration , the 1 that presently dun build on acct of gnat bug , you simply make any data structure you like in ada, and it persists to disk. )
asciilifeform: asciilifeform's mmap thing (ideally a working ver of the latest iteration, but even the original 'horsecocks') already gives ability to write simple , fast db, for uncomplicated schemas
diana_coman: if it's about wants, I can throw in that I want a sane computer already! ☟︎
asciilifeform: ideally what you'd want imho is a sane db solidly in ada, rather than coupla mil+ loc of c ??? . but this may be bridge too far just yet.
mircea_popescu: but in point of fact we gotta weld ada to db already, what.
mircea_popescu: it'd require something, that';s for sure.
asciilifeform: mircea_popescu: as i understand , this one would need either tcpism (not written yet) or unixsocketism (also afaik not written, aside from the sad adacorpse implementation in gnat std lib)
mircea_popescu: in another order : an ada prototype for db interaction, at the very least with mysql and postgres, would probably get imported into a lot of projects. anyone has one unpublished ? anyone wanna write ?
a111: Logged on 2019-01-13 14:29 mircea_popescu: this is a matter of best practices that's by its nature a republican standard candidate, so i'd very much like to hear the esteemed lordship.
mircea_popescu: meanwhile since we're doing this kinda thing, let me reiterrate the http://btcbase.org/log/2019-01-13#1886466 discussion. ☝︎
a111: Logged on 2014-08-20 01:01 asciilifeform: '…like a refugee from very rural Pakistan who gets relocated to Oslo, Norway, and still thinks that he could make better food if he were only allowed to light a fire in his living room instead of using that complex electric stove. (This is a real news item. Every now and then, landlords discover indoor fireplaces and occasionally the “newbies” to civilization burn down the building.)' (herr naggum)
asciilifeform: the 'bootstrap to c + linux' people make this exact mistake. 'look, i wrote this compact bootstrapper, nao i can breathe out and start wallowing in my familiar pointerolade an' nulltermstrings pigsty again'
asciilifeform: there was an old mircea_popescu piece , where , 'some people - stupid in particular way, and think that if they buy big enuff house, it will never have to be cleaned'
mircea_popescu: hence the profanity.
a111: Logged on 2019-03-18 15:31 asciilifeform: http://bvt-trace.net/2019/03/mes-part-1-stage0/#selection-29.94-29.340 << imho ~100% of the attempts on record , made exactly same mistake -- they assumed that 'architecture-specific aspects creep into the design of the boostrapping process' only concerns ~what is there~ in the arch, and not ~what is not there~ (e.g. sane memory management, type tags) . if you dun put the complexity of certain necessary sanities where it belongs -- i
asciilifeform: in re bootstrappers, i'll also add that the problem itself is disastrously misunderstood by most folx who tried hand at it, specifically in http://btcbase.org/log/2019-03-18#1903170 ☝︎
asciilifeform: imo peh is considerably closer to a tabletop model for sane iron cpu, than to bootstrapper for x86 etc
mircea_popescu: as i said, i'd like to keep this open.
asciilifeform: i would not presently go as far as to say 'peh is ~the~ bootstrapper' ( current peh cannot even output a raw byte... ) but suspect that the solution will have approximately its shape.
mircea_popescu: "oh but mp, this is undemocratic -- some programming styles or high level assumptions will result in ~unusable tapes, 1mnx bloated". "precisely." "but this means not all programmers aree equal anymore". "duh"
mircea_popescu: in any case, a very tentative possible repoublican alternate machine can be already intuited : if p backend is welded to gcc;s frontends, one can code in ada (or c#, why not), compiler for p-machine and live happily ever after.
mircea_popescu: if peh can be its own bootstrapper quite so transparently nobody notices, then maybe it is actually a good general purpose bootstrapping tool. maybe.
asciilifeform: no good reason imho to try to keep c on life support in long term. it's done enuff damage to the field.
mircea_popescu: asciilifeform, yes! in the other perspective : BECAUSE IT IS ITS OWN BOOTSTRAPPER!!!
mircea_popescu: but consider the converse problem : if it comes to it, am i going to order the re-implementation de novo of gcc's backend by republican hands ? why MUST it be c ?
asciilifeform: ( peh per se is a 'peh compiler', arguably, in that it can and does produce peh tapes as output, this is how e.g. keygen worx )
mircea_popescu: no argument there.\
asciilifeform: mircea_popescu: it is entirely conceivable that someone may want to bake 'peh compiler' . but intent of design is specifically for it to be entirely usable without any such thing, with reasonable effort.
asciilifeform: ( in fact ada per se has a fascism knob that, if set, prevents early return from subroutines . i have not thus far used, cuz in ffa per se this is already the case, nuffin gets to terminate early when 'constant time' algo )
mircea_popescu: (note also, but importantly, that one doesn't have to write peh by hand anymore than he has to write asm by hand. there's perfectly conceivable one has an optimizing pehpiler.)
mircea_popescu: but perhaps this is the place to find out.
mircea_popescu: it's also not yet so clear that it's worth doing.
asciilifeform: note that just about any iterative algo can be rewritten in this form. ( just that ~nobody ever bothers , typically )
asciilifeform: all of this, is to 1) make easier to 'fit in head' the flow of a pehtape by eyeballing 2) reduce cachemiss sidechannel chatter
asciilifeform: all subs have 1 valid termination point, there is no early 'return'; ditto loops ( as of ch18 )
asciilifeform: in re peh in particular, the 'tape' model i picked consciously, and not simply in re the terminology to call the proggies 'tapes'. thing is built so that all motion is , albeit non-monotonically, forward ( e.g. subroutine can call another sub, but only one defined ~earlier on the tape~ from the place where called; and all subs ~must~ either reach their termination point, or produce verdict & halt the process , there is no 'goto' )
mircea_popescu: this observation is a major driver of the foregoing.
asciilifeform: mircea_popescu: right. and , interestingly, the coupla-1000fold diff b/w main ram speed and that of cache , on current-day irons, has just about brought back the age of tape algo
asciilifeform: ( recall incidentally the fate of 'bubble memory.' mega-invention, btw. d00d discovered that you dun need a tape deck to use tape, in a certain config of magnetic field, you can make the bits on tape ~walk~ in circles. and r/w'em as they move past a particular spot. )
mircea_popescu: but we are very specifically not discussing what to do to read trilema. we're discussing what to do at a relatively early stage of bootstrap!
asciilifeform: all of this being said, i suspect mircea_popescu would still barf if to e.g. fetch a trilema pg, 5km of tape had to move a full circle.
mircea_popescu: because no, this is a cop-out, "oh, it's arbitrary". like the poorly trained cook, "arbitrary use of tools"
asciilifeform: you can do a surprising amt with N tape decks that ordinarily 'demands randomaccess'
asciilifeform: where he had the 'algos for N tape decks'
bvt: mircea_popescu: i'll try to get him into #trilema on the weekend
mircea_popescu: yes, it is, translates bizarre pantsuit notions of "randomness" ; nevertheless the point stands if renamed : arbitrary, and who's the arbiter ? Nike the goddess ?
asciilifeform: mircea_popescu: the 'random' in 'random access' is imho an unfortunate misnomer.
mircea_popescu: obviously (i would hope) i'm not proposing any naive solution will necessarily work well ; i'm just saying that it's not obvious to me a smart solution isn't available somewhere. in point of fact not merely p, but ~the whole class of things for which it stands as a most illustrative example~ is, if arguably not new, in any case the continuation of work in fields and along lines neglected for at least three if not more than
mircea_popescu: but in any case no such thing as "random" exists in the fucking machine --- if it did, you wouldn't need to buy fg's for it, now would you.
mircea_popescu: the dood's historical blackjack playing program is a better model of "bootstrapper" than what you find in average "systems design" in orclang books.
mircea_popescu will import by reference the story of mel. what "random access", it's onlty random if you don't know what you're doing and at bootstrap phase the item's too close to starting position to have complexity-exploded out of your hands already as a matter of necessity.
mircea_popescu: i'm not disposing of the matter. i'm just keeping it open, and specifically because these sorts of things are by now reflex in the malfunctioning brains of "it experts". oh, small ram footprint of bootstrapper. oh, random access.\
mircea_popescu: yet maybe you don't actually have to.
asciilifeform: or a 2pass compiler. or anyffin that gotta walk a substantial length of bits >1ce
asciilifeform: mircea_popescu: per the current instruction set, you could not write e.g. 'unzip' in it
mircea_popescu: it's not directly obvious to me that "random access" in this particular context is not disease sympthom.
mircea_popescu: ie, being economical re bootstrap ram is one of the dumbest things i can think of. beats "penny wise and pound foolish" by 2+ degrees of magnitude in folly.
asciilifeform: mircea_popescu: there's other constraints, e.g. peh is quite certainly not optimized for random-access on large data set , there is no support for even such thing as array