log☇︎
44200+ entries in 0.027s
a111: Logged on 2019-02-20 15:02 mircea_popescu: trinque did you ever see the guy irl lately ? say this year or something ?
trinque: http://btcbase.org/log/2019-02-20#1898077 << he's alive and well, sinfully busy atm helping me chase down some cash. sends his regards to the republic ☝︎
asciilifeform: (c) is generally not an option in lightweight ('scripting') langs, so these generally end up (a)
asciilifeform: Mocky: they forgo threading cuz on c machine you have exactly 3 options : a) forgo threading (i'ma not detail python's 'forgo threading and then lie about it' as separate variant, it is beneath contempt) b) sit down on unix's threads (pthread) c) implement own scheduler
Mocky: but i don't have asciilifeform's mental model of a much better lang with which to compare. I have c c++ python javascript that I also get paid to work with occasionally, which ~entirely punt on threading
asciilifeform hopes to live long enuff to stop cleaning up piles o'shit for a living, but not holding breath
asciilifeform: some things are simply steaming piles of shit, from which there is nuffin to say, and the only use of which is that one can make a few bux cleaning'em up
asciilifeform: Mocky: i sympathize re that you toiled in it for 20y; for my part , i work with... microshit kernel diddles etc, for bread. but i'll be the last to say 'here's what we can learn from microshit' (afaik there is ~0 to be learned from microshit, other than how to run the hell away)
asciilifeform: afaik java simply aint 1 of'em tho.
asciilifeform: there ~are~ dead langs that got something right.
asciilifeform: i mention this strictly cuz we're apparently doing a 'dead langs' thrd
asciilifeform: the threads (they were 'lightweight', i.e. zcx-like, things, but with termination (and restart!) mechanism) were snapshottable objects, to the extent that the runtime knew how to move'em between not only cpus but machines, and in such a way that the proggy continued w/out interruption (if e.g. machine catches fire and its threads gotta move before fire reaches cpu etc)
a111: Logged on 2017-03-30 14:50 asciilifeform: trinque: erlang wasn't simply about 'uptime', or even 'no pointer arithmetic', it also was the only case i know of where process migration actually worked
a111: Logged on 2017-03-30 14:43 asciilifeform: anyway erlang is imho only worth discussing as part of a larger pattern -- industry after industry independently discovered that c -- and its entire approach to logic -- is poison
a111: Logged on 2017-03-30 14:38 asciilifeform: mircea_popescu: i will also nitpick : 'erlang' does not belong in the list, it was a 1980s product that worked quite well in its industrial niche (large telco switches) but was later stolen and used as a totem by the folx from yesterday's thread ( http://btcbase.org/log/2017-03-29#1633873 )
a111: Logged on 2015-06-22 21:22 mircea_popescu: ascii_field this goes right into our discussion about how the only reason lisp is ok where c is shot is that the hordes haven't sat on lisp but on c, would have been the other way around if they had sat the other way.
asciilifeform: Mocky: not a 'puzzle lang', tho i can see how you might've come to the conclusion ( it's been suffering from heavy case of http://btcbase.org/log/2015-06-22#1172831 ) ☝︎
Mocky: erlang I did look at briefly, but not the concurrency, seemed to me like a puzzle lang
Mocky: fortran threading I never looked at, but will. pretty sure threw away all my punch cards tho
Mocky: iirc that was after backus turned to shit in committee
asciilifeform: or even erlang's thread machine
asciilifeform: or if you gotta explicit thread, ada's tasks in sjlj mode ( or even zcx , if you dun care re terminations )
Mocky: serious question asciilifeform, where do I look to see better threading that java. I honestly dont' know
asciilifeform: ... which means they're liable to all end up on 1 physical cpu, lol ☟︎
asciilifeform: cuz they dun map to native threads
Mocky: also threads in infinite loops can always be stopped on every platform
asciilifeform: sounds like reads locked by default then
Mocky: i wouldn't argue that explicit threading is good. but instead of concurrent i++, consider concurrent assignment to heap references, even without locking always have a valid reference, never a garbage pointer, no matter how many threads or cores
asciilifeform: ( ever wonder wai fortran still in use at '9000 cpus' massively parallel comps ? this is why )
asciilifeform: srsly the ~fortran~ people understood this. in 1990.
asciilifeform: explicit threading is ipso facto sad.
asciilifeform: i found the thread model just as ridiculous as that of pthreads.
Mocky: i've seen dozens of those. look equally shit on every platform
Mocky: I'm not defending java, I'm stating that in addition to pile of shit, theres a coherent memory model, thread model that is not agony to work with.
asciilifeform: *to this day
asciilifeform: ( or where promised 'portable' but this this day i've never seen a gui proggy in java that runs on >1 os w/out modification. and etc )
asciilifeform: ... and where they added iterators 15 yrs after lang released, to great fanfare
Mocky: yeah, early java lists were shit in that way but no more. now shit in diff ways
asciilifeform: arguably managed to ~add~ retardation on top of ordinary cmachine, no mean feat
asciilifeform: eh it's the lang that made e.g. integers a 'non-class' object and thereby non-storable in lists etc
Mocky: so not optimal, maybe even laughable, but yet has a model and as spec that is not self contradictory
asciilifeform: i dunthink ~standard~ cpp exposes threads ( maybe cpp14 ?? )
Mocky: laugh if you will, yet still can't do it even *with* locking in standard c++, as far as I can tell
Mocky: and yes can increment global and local counters in threads and have it add up, but requires locking or cas
mircea_popescu: Mocky just trying to evaluate if this thing worth digging up
Mocky: i'm not saying they solved threading once and for all, or that eliminated deadlock. any system that allows you to acquire locks in different order can be deadlocked. i'm just saying that there are concurrent primitives that can be understood and which have guaranttes that hold
mircea_popescu: but the ensemble will not move at the speed of a single core will it ? ☟︎
Mocky: can do multithreaded i++ and never get garbage, if you mark it volatile forces read and write to main memory
asciilifeform: and i wrote 9000 proggies that produced diff answer erry time they ran depending on what the thread gods felt like that day
mircea_popescu: Mocky so if i declare a procedure which increments a global and a local counter, and then call it in a loop from multiple threads, at the end the globa lflag will contain the sum of the local flags ?
asciilifeform: dunno, the multithread java they had us homework at uni, deadlocked as easily as farting.
Mocky: there are explicit and implicit semantics, but if you read the spec, you know what you'll get. multiple threads setting a value on the same variable never create garbage
asciilifeform: Mocky: coherent how ? iirc thing still relied on explicit semaphorism
Mocky: I mostly agree. They did manage a coherent threading model / memory model which turns out to be the thing I miss when I'm writing in something else
asciilifeform: Mocky: imho all of javaism was a massive exercise in 'just want to'ism
a111: Logged on 2019-02-20 15:50 asciilifeform: really oughta have ~1~ compiler, and for a sane arch; and if yet cannot afford to actually siliconize the sane arch, then the sad iron oughta be booting straight in bios to a compact (asmistic) emulator of same
Mocky: i mean, entire jvm is c/c++ and filled with c/c++isms so not exactly in the direction of http://btcbase.org/log/2019-02-20#1898128 , more in the direction of 'just want to' cross platform ☝︎
asciilifeform: a good thing, too
Mocky: I was hopeful back in the day at java chip and java os, nothing worthwhile surfaced
a111: Logged on 2019-02-20 16:08 asciilifeform: various folx attempted something roughly like this, but succumbed to own idiocy -- e.g. the java people, who 1) wrapped their 'vm' around the nonsensical shape of their tardlang 2) stopped short of 'and no this doesn't run on your tard os, is IS the os, fuckyou' ;
Mocky: http://btcbase.org/log/2019-02-20#1898149 I know of a couple attempts at java os, one I installed on my Compaq iPaq in 2002. but they were shit ☝︎
BingoBoingo: Dead cop further down page than dead graffiti communist punk
BingoBoingo: A bit deeper "Uruguayos no somos Latinos, somos Europeos": "Mi amiga tuvo un hijo en EEUU hace un tiempito y cuando lo van a anotar, dentro de las cosas que ponen en la partida es raza (WTF EEUU??!), la administrativa no quería ponerle "caucásico" así que le puso Latino white o una onda así."
BingoBoingo: From the mines: "Viví 6 meses en Madrid y varias veces se me rieron en la cara (la mayoría empleados públicos, y una vez en un banco) por mi manera de hablar, pero mi peor experiencia fue en entrevistas de trabajo donde me dijeron que el problema era que no hablaba español." - Some Uruguayo
hanbot: right right, i mixed 'em up. and yeah, i'm planning on grabbing phf's keccak v.py in step 3, if only because i've seen diana_coman's pop up in cuntoo tests so i'd like to test the ver less traveled.
asciilifeform: ^ also had a vtron. but then sank to the bottom of the sea, so unmaintained afaik.
a111: 2018-10-23 <esthlos> http://btcbase.org/log/2018-10-19#1864316 << apologies alf, I'm running behind! trying to gather time to get caught up in the next week or two
asciilifeform: hanbot: v.py actually exists in modern ( keccakistic ) incarnation -- there's 2 variants, largely identical , diana_coman's (the 1 i use now) and phf's (he had some incompatibility in his python iirc which required own variant)
mircea_popescu: hanbot write down the whole story as you go, but basically yes.
asciilifeform: hanbot: it is also possible to bootstrap any vtron using naked gpg, ancient gnupatch, and bare teeth ( manually check sig and patch -p0 < foo.patch, for ea. )
hanbot: where "knows to v" = "knows no v". heh.
hanbot: in bootstrapping adventures, it looks like the flow for a machine that knows to v to get vtools going is like so: grab some ancient v, ie mod6's v.py, use it to press phf's vtools vpatch, then eat phf's v.py "updated for vtools", then press vtools to keccak head. anyone feel like spotting this for me?
BingoBoingo: And across the river Argentines can't afford coca-cola anymore https://www.elobservador.com.uy/nota/argentina-coca-cola-femsa-anuncia-reestructura-laboral-por-baja-en-el-consumo-201922018333
asciilifeform: i find it hard to picture how a sane cpu, where optimizing compiler is 10k loc and 'fits in head', could have no market. but then again the bolix people proved that it ~is~ possible to go broke with one.
asciilifeform: ( would want a windowed / microscopable die, naturally, if actually did this, or how wouldja audit )
asciilifeform: (e.g. FG, for instance, was drawn up from the start to be siliconizable w/out any major change, if/when time comes)
asciilifeform: we dun lack the 'how' ; if mircea_popescu commissions an iron, i'ma draw up an iron. q is how to massage to pay itself.
mircea_popescu: conquering china, also expensive. who knows, maybe it can be massaged to pay for itself.
asciilifeform: iron ? the most delish, imho, spot conceivable. but -- expensive.
mircea_popescu: kinda makes it a particularly delicious spot to rape the femstate.
asciilifeform: ( current pc arch 'standard', to the extent it exists even, is a microshit authorship )
asciilifeform: likewise you can't buy a southbridge that dun do the acpi liquishit, cuz again microshit decree.
asciilifeform: you can't, for instance, buy a x64 that ~only runs in 64 mode~ : no, you gotta have the (broken) msdos compat, inner 386, etc. cuz winblowz.
a111: Logged on 2016-01-19 21:55 ascii_butugychag: the whole point of engineering is to cut apart the happenstance-linked crud from what you actually want.
asciilifeform: i.e. nobody http://btcbase.org/log/2016-01-19#1377640 them. ☝︎
asciilifeform: the worst thing, imho, is that the 'baseless distinction' is quite often 'in one strand' with actual distinction -- e.g. the 'speshul olympics' of x86 vs arm : both are shit archs, but 1 has 35 yrs of compat-crud, and eats 100x the wattage vs other
a111: Logged on 2016-06-14 14:12 asciilifeform: did we ever do a screw threads thread ?
a111: Logged on 2017-04-09 23:14 mircea_popescu: "who do you think will win, mr 13, the team with two guys and monkeys or the team with three guys and monkeys ?"
mircea_popescu: there MAY NOT exist "conflict" on baseless distinctions, which goes right the fuck into the whole http://btcbase.org/log/2017-04-09#1641209 ☝︎
mircea_popescu: ie, whenever you encounter "competitions" of malformed nonsense, you're exactly in the position of the ~spectator~ to special olympics.
mircea_popescu: i suppose the pov where design is ~constrained~ activity, and the concept of "design competition" must strictly describe a situation where machine a with 64 registers of which one is mask and machine b with 64 registers + ONE separate mask register compete.
asciilifeform: writing sane compiler targeting e.g. x86 is not entirely unlike dancing ballet while carrying 50kg weights
asciilifeform: this is quite typical example.
asciilifeform: the tard arch people passed the 'register killing' ball to compiler, as result bloating ~all~ compiler with massive gnarl, ~just for reg killing logic~
asciilifeform: and , mircea_popescu , this is just the needle point on the tip of retardation iceberg.
mircea_popescu: as a general design principle! you may NOT have "multiple" on a machine. it's 0, 1, buswidth-count. THAT IS IT.
mircea_popescu: let me guess, the same fucking people who made mul without carry.
mircea_popescu: http://www.loper-os.org/?p=46#selection-47.1021-47.1284 << this, incidentally, is a fine example. who THE FUCK came up with the notion of making "registers" ~without~ making a) as many of them as the bus width and b) a special register which keeps a mask of registers, so that PUSH only actually occurs if needed ?
asciilifeform: currently i suspect that the corpse of tcc is 1 of the moar fuckable corpses in the unixtardation graveyard, tho.
asciilifeform: but i think i get mircea_popescu's pt