Readit NewsThe floppotron
Maybe this is what you're referring to. There are similar examples where people do this with old disk drives and printers too.
Almost but not quite. The speed of light is always the speed of light. There's nothing wrong with gamma rays.
It's charged particles such as beta and alpha rays that generate the blue Cherenkov radiation. The writer's link to Wikipedia already reflects that.
The big FPGA players have mostly quit that shit; AMD/Xilinx, Intel/Altera/Whatever dumb name its about to be spun back out as, and Lattice all have free versions of their dev tools for at least their parts small players can afford. They just want you to buy chips and IP.
I haven't heard of the Yosis folks making a PolarFire backend, so I don't think there's an open alternative.
Libero is even FlexLM based licensing like the bad old days of proprietary dev tools.
HDLs have familiar syntax that makes it seem like you can just program algorithms imperatively (for loops, if statements, functions etc) but it's all just a mean trick to catch software people out, and generally won't give the results you expect.
On top there's then the fact everything happens at the same time, the faff of making everything synchronised and making sure it meets timing and fighting the frankly awful tooling every step of the way.
Once you get it, it's fine, but you have to unlearn a lot of software muscle memory and keep the actual design work (boxes and lines) almost entirely separate from the implementation (typing your boxes and lines into a text editor).
The bishops are limited to half the board so only need 5 bits for position. This frees up 4 bits, but you lose the capture state (can't use King's position for capture state). Well, you CAN use the king's position for capture state for two of the bishops at any given time. Then for the other two bishops use a bit to store their capture state. This saves 2 bits overall, bringing the total down to exactly 26 bytes.
Gonna have to think that through for awhile, not sure if it works out.
Update: I see a comment below that does this but uses 21 bits (instead of 22) by storing bishop position and capture state as a base-33 number.
Might sound a bit niche, and it is, but even if you ignore the stuff about actually certifying stuff to fly, it has some extremely useful and interesting tidbits about how to go about running very large and highly complex hardware/firmware projects in safety critical industries.
The chapter on requirements is especially useful, and the whole thing is written in a (relatively, for the topic) light-hearted way.
We all take on culpability for certain harms to others. It’s just a question of what as a society we are willing to accept.
I don’t think this is an issue of society “overlooking” the morality of this specifically. It’s just that people have a lot of problems to worry about, and the crash safety of large vehicles isn’t high on the list.
https://en.wikipedia.org/wiki/Royal_cypher