asciilifeform: mircea_popescu: a good chunk of what i've done here since showing up is to try and fill in the gaps in the 'pioneer with arrows in his back' part of my www.
asciilifeform: phf: linux wasn't trying to multiprocessorate every arithmetic instruction etc.
asciilifeform: i have the dead trees, they fill most of a shelf.
asciilifeform: which is not at all like the naive, reasonable conception pictured here.
asciilifeform: yes. and it made sense to me in '07. but not in '10 when i understood how the actual extant pc iron works.☟︎
asciilifeform: no, it was a ~reasonable~ point, but when you go and try to actually implement it, on actual iron, it drives you to nuttery. because the thing is encrusted with unfathomable layer of undocumented turdolade and 'no this doesn't actually work, because fuckyou'
asciilifeform: let's say the 8 cores operate on same memory location. how do they maintain cache coherence when writing output ?
asciilifeform: mircea_popescu: it dun work because, again, pc arch is retarded. the processors fight over the bus.
asciilifeform: mircea_popescu: believe or not, i thought of this.
asciilifeform: things that the silicon ought to be doing. and ~WAS~ doing in 1976.
asciilifeform: mircea_popescu: understand, addition there is no longer 'ADD rax, rbx' but a pound of type bit checks and possible code paths on failure or type-promotion etc.
asciilifeform: pointing out that the intrinsic complexity far exceeds linux, bsd, whichever c os, kernel.
asciilifeform: and if you use ANY 'c code in the drivers' you get gabriel_laddel.
asciilifeform: mircea_popescu: the two are really not comparable.
asciilifeform: mircea_popescu: try to understand that linux is barely a thing at runtime. whereas a lisp os has to make up for 10,001 idiocies of the hardware, e.g., lack of garbage collector, lack of type bits in every (yes) machine word that get tested on every (yes) arithmetic operation, etc.
asciilifeform: but mircea_popescu has it, the sane approach involves 0 c and 0 unix, and i came to this conclusion in '07.
asciilifeform: phf: why take my word for it, thing was published, eons ago, read.
asciilifeform: phf: a MB of hand-written asm, and reliance on x86-32isms, e.g., segmentation, is 'married'.
asciilifeform: movitz is worse yet because it is ~married~ to 32-bit x86
asciilifeform: and the hardware ~is~ shit. boot up one of these (if you can actually get it to boot.) and say hello to 1 fps graphics, disks without dma (you don't know what these feel like until trying personally), nic that works when the moon is full strictly, etc.☟︎
