asciilifeform: in general, the tumour mass of 'i have 200 utils that do ~same thing on my box, and not a single one ~quite~ works entirely' is to be flamethrowered.
asciilifeform: one - proper one - suffices. and it is easier to produce from a generalized vtron, than to produce a vtron from, e.g., 'redo'.
asciilifeform: erlehmann: it isn't clear to me that these belong in separate programs, and that a system ought to have two tree walkers.
asciilifeform: ( so long as the signers, sign the hashes, and you still have a cryptographically healthy frozen history -- it is entirely acceptable to specify also how the inputs are to be produced. )
asciilifeform: current vtrons assume that all of the signed nodes exist on disk already.
asciilifeform: and they'd trigger, if hash not found immediately. and so you get a maketron.
asciilifeform: can easily have process invocations (e.g. compiler invokes) rather than filename-hash
asciilifeform: thing is, nowhere is it written that a v program ~must~ be a gnudiff-like thing
asciilifeform: if a vpatch refers to a hash of a nonexistent file, the process stops.
asciilifeform: erlehmann: what means to walk 'non-existence dependencies' ?
asciilifeform: so intel shat out ht, aka 'i can't believe it's not a cpu core'
asciilifeform: was introduced right when moore's law first was beginning to sputter out, and new ways of bamboozling idiot new-iron chasers were being devised - 'let's up the clock speed but cut the work per-cycle', etc
asciilifeform: even on chips where it did not cause halt-and-catch-fire, it was always a sort of hardware equivalent of ye olde 'ramdoubler' scamola -- 'make luser think he has 2x the cores'
asciilifeform: but the generalized, correct incarnation of 'automatic dependency graph walker' is : v.
asciilifeform: gnumake is one of those turds that ~every serious user, eventually tries to rebuild, out of whatever is at hand, because of sheer barfalicity
asciilifeform: erlehmann: http://btcbase.org/log/2017-06-26#1674460 << 'redo' is theoretically neat ( at least when compared to gnumake ) but - and i studied it, since you last mentioned it - it strikes me as a near-miss attempt to invent 'v'☝︎
asciilifeform: who was interviewed over email for this story, said he “cannot comment on individual decisions and personnel matters,” other than to say that all personnel matters were “handled in accordance with Institute HR policies.”' )
asciilifeform: ( https://archive.is/Tr9PF , linked within, also interesting : 'Led by IS&T’s vice president, John Charles, the ambitious reorganization began in February 2015 and aims to spur innovation through agile software development practices adopted from industry. Charles emphasizes that this is not a typical reorganization, but rather a complete transformation of MIT’s IT department. ... Many longtime employees have resigned ... Charles,
asciilifeform: or, alternatively, desperate usg dod-like last gasp to keep massive fleet of winblows boxen properly declitorized and infibulated
asciilifeform: 'Instead of being renumbered into publicly-accessible IP ranges, IS&T is moving all of campus into RFC-1918 10/8 addresses, and enforcing the campus firewall, which will be made up of Palo Alto 7050 devices, which are best known for their deep-packet inspection feature, App-ID.' << ahahaha so it ~is~ about zapping unauthorized nonethertardium nodes etc
asciilifeform: picture 'upper half of british crown's jewels will be sold...' mentioned in passing in some unrelated crud
asciilifeform: 'Although the ranges sold initially were unused, IS&T announced that the entire upper half of MITnet would be sold, and that buildings would need to be renumbered.' << holy fuq mircea_popescu was right
asciilifeform: hey, they gotta keep inmat^H^H^H^H^Hstudents from hosting warez/trb/etc terrorisms somehow!1111
asciilifeform: until IS&T suddenly and unceremoniously decided to renumber all of campus onto a private, NAT'd address space. Some buildings have already been migrated, with same-day notice, causing outages of services hosted in those buildings.'
asciilifeform: 'Ever since IS&T started to undergo "The Transformation", there has been a deliberate and systematic attempt to change Computing at MIT for the worse. Services that have been relied on for years have been discontinued and turned down, frequently without notice. Infrastructure critical to running MIT has been outsourced to cloud services during "emergency maintenance". Most of these changes had minimal impact on students and faculty,☟︎
asciilifeform: TomServo: lulzy. see also the infamous light bulb.
asciilifeform: http://btcbase.org/log/2017-06-26#1674428 << fwiw i carefully read all of it. asciilifeform's verdict: very much a gabriel_laddel-ization of gossipd. does 0 of the necessary work, and drags in 5+GB of liquishit deps (python, sql, some derp's crypto lib.) the amount of this that would have to be rewritten, from the ground, is 100%. not even useful as illustration of anything, because NONE of the actually complicated moving parts of a☝︎☟︎
asciilifeform lulzily, and almost polar oppositely of js-of-mp -- is in nyc
asciilifeform: sometimes people write to asciilifeform , 'you're a bore and pompous arse', but fwiw i have to date 0 posts about dieting. or about Eating Eggs While 3133337.
asciilifeform: 'betcha you can't surpass taleb in militant self-aggrandizing mundanity' 'you have yerself a bet!!11'
asciilifeform: and holy shit pete_dushenski... that post. i'ma guess you are writing these on a bet
asciilifeform: ( which in asciilifeform's case was ' can crypto be put on a hard scientific foundation - i.e. does a provably hard problem exist )
asciilifeform: phf: re goldreich -- a very specific and deep type of downer, where you find what by all appearances is the definitive, unsurpassed definitional stem of work in $field -- which turns out to be wholly and deliberately useless on $principalquestion
