asciilifeform: this is the naggum-cpp problem all over again -- we do not know, when beginning a project, the ultimate granularity.
asciilifeform: mircea_popescu: knowing into what granularity thing must break, would require being able to tell the future, neh
asciilifeform: and now would like to represent this transform without destroying structure.
asciilifeform: trinque: but let's say i take a routine from earlier ( e.g. unrolled comba mult ) and the rest -- from last week's
asciilifeform: trinque: not necessarily, could even store the lines individually, rather than as single text string, and generate the html soup in variants depending on number in url
asciilifeform: trinque: i have nfi if what i asked for, can be done with extant www shitstack
asciilifeform: in particular, related items gotta be near
asciilifeform: readable is when structure is maximally preserved.
asciilifeform: 9000 posts containing almost-same item, is not anyone's idea of readable
asciilifeform: ( even with mircea_popescu's script, if the code is changed, the links are mutilated )
asciilifeform: diana_coman's item is moar or less the right thing, except that it is impossible to link to individual line
asciilifeform: if a wwwtronicist ( ben_vulpes ? ) were to come up with a method of dropping ada into wp and getting out an item that doesn't wrap or truncate lines, destroy numberings, and allows linking to individual rows -- i will take off my hat
asciilifeform does not disagree with any part of this
asciilifeform: this item calls for something like phf's v-viewer☟︎
asciilifeform: and line numbering is destroyed every time thing changes
asciilifeform: mircea_popescu: syncing a wp turd with coad on disk, in flux, is a bitch tho
asciilifeform: i was just thinking about this, this morning, during the 'declare' thread -- wanted to link to a particular item in ffa, and realized that i couldn't
asciilifeform: i've enough trouble keeping track of 9000 mutually contradictory variants of every possible thing, on own disk
asciilifeform: pretty sure asciilifeform typically eats moar space in l0gz per paste, than paste weighs
asciilifeform: ( runtime generic instantiation certainly did not exist, and really has no analogous item in any other statically compiled language afaik )
asciilifeform: neither did modular types of arbitrary bitness, and several other minor nuts and bolts of ffa, that i cannot immediately recall.
asciilifeform: the 'declare' construct mentioned earlier, also iirc did not exist in traditional pascal
asciilifeform: ada ( even asciilifeform's 'fascist' ada subset ) is not exactly pascal. imho the most notable departure is the array slice abstraction, which makes for a 90% moar compact ffa ( and applies to almost anything else dealing in bitstrings, for that matter )
asciilifeform: diana_coman: you can painlessly abolish 99% of where typical cprogramming victim would use a dynamicism, by use of the declare-begin-end construct to allocate statics on the current stackframe
asciilifeform: sorta like asciilifeform's discovery few yrs ago, where turned out that e.g. lathe was considerably easier to get in '50s than today, but 'hey , hurr , 3d printers!!' etc
asciilifeform: gotta wonder, how many other 'hey it's soo cheap and available!' technomarvels, on examination would turn up to be exactly same as this
