log☇︎
161700+ entries in 0.471s
asciilifeform: the fact that reiser was jailed cemented it as permanently high-quality, no one wants to touch it, no 'progressors' progressate at it, no gnomes, no popularizers!111, etc.
asciilifeform: with 0 issues.
asciilifeform: jurov: i've been using reiserfs for ~decade.
asciilifeform: and much as i loathe the idea, we will probably have to nail down our own linux distro.
asciilifeform: instruct new users that they must operate on a sane fs.
asciilifeform: anyway this particular crapocalypse is avoidable, at least on our planet. BAN any heathen fs.
asciilifeform: see also the gcc5 threads
asciilifeform: gotta love these 'optimizations'
asciilifeform: though i have it
asciilifeform: i did not include the tcp module for ts either
asciilifeform: phf: this was on my list of things to include, but i wanted to 'take it slow.'
asciilifeform: srsly, we are there already ??
asciilifeform: 'i deleted this first before reading, faster!1111'
asciilifeform: show me example ?
asciilifeform: glorious!
asciilifeform: msdos ?
asciilifeform: jurov: what do you have with different filesystem semantics ? vax ?
asciilifeform: any future folks who might think they are being clever with, e.g., nonterminating vtron program.
asciilifeform: we have finessed the halting problem !1111 ☟︎
asciilifeform: there is exceed-bound-and-i-negrate
asciilifeform: jurov: the magic trick is that there is no such thing as unbounded runtime on my box.
asciilifeform: it is almost exemplary of the opposite of what we need here.
asciilifeform: and srsly, 'ed' ?! not meant for human reading any more than 'patch'.
asciilifeform: hence turingcompletevtron. ☟︎
asciilifeform: i demand X, even values of X i don't yet know about.
asciilifeform: and i'm not very interested in 'can do all but X' widgets.
asciilifeform: jurov: i've looked into everything.
asciilifeform: but i can't promise this, and can't be bothered to test, for reasons already described.
asciilifeform: from my naked eye reading, your thing will run until the first gc cycle.
asciilifeform: he is free, and encouraged to, produce his own schismatic shiva, and sign it, and who knows, folks may come to prefer it to mine.
asciilifeform: the magic of 'v' is that polarbeard does NOT have to agree with me!111
asciilifeform: and also in case polarbeard missed last night's thread,
asciilifeform: (for n00bs or readers who have not been keeping up, 'shiva' is a highly experimental affair and not to be considered part of mainline trb!)
asciilifeform: but yes, in the long run it is intended as a prosthesis to take over where the brain damage of the original is incurable.
asciilifeform: for the time being, with the more modest goal of abolishing the rpc module.
asciilifeform: nobody asked you to. but try also refrain from translating shiva to cpp, and spreading the leak metastases into it ?
asciilifeform: 2) to THERMONUKE the idiot leaks.
asciilifeform: 1) to have the cpp content of trb asymptotically go to ZERO with time
asciilifeform: the point of shiva is PRECISELY the opposite
asciilifeform: (not to mention, bloating the code, but this is secondary)
asciilifeform: is that by 'marshalling' the pointers, you are introducing trb's leakages into tinyscheme.
asciilifeform: see, the big thing here,
asciilifeform: and i hope this is good feedback.
asciilifeform: but doings in cpp what can be done inside tinyscheme, i will not.
asciilifeform: these i will happily read, and sign.
asciilifeform: please do.
asciilifeform: anything that is not going there, must answer why.
asciilifeform: on the contrary, that is the ideal place for all new code pertaining to shiva.
asciilifeform: for another, bug fixes are their own patches, one per bug, that must contain nothing else.
asciilifeform: for one thing, i won't be implementing list reversal in cpp !
asciilifeform: i did give example.
asciilifeform: it is an example of everything i stand against. ☟︎
asciilifeform: but it is also not an anything else.
asciilifeform: i do
asciilifeform: if you found an ACTUAL bug, that should be OWN PATCH.
asciilifeform: WHAT BUG
asciilifeform: do you know what an explanation is ?
asciilifeform: this is not an explanation.
asciilifeform: and what is this ? >> https://gist.github.com/polarbeard/f5c5b02a2ce7c1a69c77#file-shiva_hooks-patch-L142
asciilifeform: shiva.cpp as i originally wrote it, includes all of the trb headers. you can form scheme data structures handily without engaging in weird cppisms, just by iterating over, e.g., the node list, and forming scheme list while you do it.
asciilifeform: WHY
asciilifeform: explain to me why it is even necessary.
asciilifeform: everything that can be in scheme, MUST BE.
asciilifeform: these should be in scheme.
asciilifeform: why reverse_in_place, mk_list, marshall, etc. in cpp ?
asciilifeform: polarbeard: why all the crud ?
asciilifeform: hm.
asciilifeform: labia majora
asciilifeform: aha
asciilifeform: i suppose if mircea_popescu tells me that it is standard, i will believe.
asciilifeform wonders about the hypertrophied labia 90%+ of porn chix seem to have
asciilifeform: it is also how you get 'no motherfucking updates ever, weld into concrete' while still getting exactly what is needed at every juncture.
asciilifeform: complete solution made from ~orthogonal pieces~ is the magic sword which weighs as a feather.
asciilifeform: any metric you like - lines, complexity, hours to read
asciilifeform: mircea_popescu: this is a misconception, in this case. weigh my tinyscheme vs gnudiff!
asciilifeform: nobody said terraforming planets would be easy...
asciilifeform: which is why turingcompletefinalsolution.
asciilifeform: (chicken was what i nowadays call a 'pedigree bridge')
asciilifeform: what a fuckingmisery
asciilifeform: specifically 'chicken'
asciilifeform: aha recall this from early trb days ?
asciilifeform: the adult version as i envision it is much more like what is described above.
asciilifeform: it was really only half-gestated.
asciilifeform: 'v' as we have it now, or at least as it appeared in my initial publication, was a very hasty and premature, wartime wunderwaffen thing
asciilifeform: well it technically doesn't have to be scheme. draft ver of 'p' for instance is more forth-like.
asciilifeform: could've guessed, aha ?
asciilifeform: no kernel, just a little scheme interpreter.
asciilifeform: because 'cover corner cases' through 'enumerated' is braindamage.
asciilifeform: but it is one of the things that must come to exist, for sanity.
asciilifeform: mircea_popescu: if this was not clear, there is not presently any such thing as turing-complete diff/patch
asciilifeform: like most open sores crud.
asciilifeform: just grew, like fungus.
asciilifeform: nor was the thing in any sense designed at all, really.
asciilifeform: and more generally, unix 'patch' output was not really designed for human eyes
asciilifeform: likewise file deletions
asciilifeform: we have this atrocity because gnudiff is incapable of renaming a directory without MORONICALLY --- -ing EVERY FUCKING LINE of every file and +++ -ing it in again
asciilifeform: mircea_popescu: this is a continuation of a thread almost as old as 'v' - consider the tinyscheme-genesis patch, shiva, and the 'pedigree bridge'
asciilifeform: it is why i settled on straight gnudiff instead of trying 'clever' things
asciilifeform: http://log.bitcoin-assets.com/?date=21-02-2016#1411879 << imho this will have to be a thing that is solved in one Final Solution shot, with turing-complete diff. we can NOT have 1,001 incompatible hacked gnudiff variants floating around in attempted use, it is chaos and death by ants. ☝︎☟︎
asciilifeform: (vs banked naturally)