I started going down the path of building a ripple carry adder already (which seems to work fine). Then I was going to try for a full on ALU, then some sort of ISA that sits on top of it all.
I have no idea what the end result will look like if it all comes together. Hopefully I'll find some weird primitives along the way. :D
It's very hand-wavy, but I'm kinda hoping I can somehow have a machine manually constructed out of neurons that can naturally interact with one built with looser hebbian learning rules.
"In the dormitories of the Jinjiang Group, the company hired by BYD to carry out the work, there were no mattresses on the beds, and the few toilets served hundreds of workers in extremely unhygienic conditions. The workers also had food stored without refrigeration.
The Brazilian Labor Prosecutor's Office (MTP) also accused the companies of withholding the workers' passports and keeping 60% of their wages; the remaining 40% would be paid in Chinese currency."
Speaking from past experience with the DoE (I'm happy I don't need to deal with security like this anymore), there were constant and randomized checks to make sure fiber cables (they were all fiber to make it harder to tamper with and to avoid accidental RF) were fully visible (e.g. not hidden under a desk or something) and not tampered with. Also, lots of locks and doors, both electrical and mechanical. The guy at the front desk with a big gun probably helped too.
They have multiple networks. One of them is definitely airgapped (red for RD). The medium security one is protected by annoyingly strict network ACLs (yellow for ITAR). Then there's a low security one for stuff like sharepoint (green).
It's very similiar. The rod logic in diamond age (Eric Drexler was the one who originally came up with it) moves linearly -- not rotationally like this does. It's also reversible.
Yeah, it's definitely a significant shift. The Xinfra component helps with Kafka compatibility, but that still has quite a bit of complexity to it. Also, it's written in C++, so that requires a different mindset to operate.
> do you think GCC’s m68k backend (to pick an arbitrary one) has been as battle-tested as their AArch64 one
m68k might be a bad example to pick. I was using gcc to target m68k on netbsd in the mid 1990s. It's very battle tested.
Also, don't forget that m68k used to be in all of the macs that Apple sold at one point before they switched to powerpc (before switching to x86 and the current arm chips). You could use gcc (with mpw's libs and headers) on pre-osx (e.g. system 7) m68k macs.
https://hpc-tutorials.llnl.gov/flux/