I recently tried Kaitai for something like this. It worked for some nontrivial cases, but I felt like I kept getting bitten by syntax limitations. All the way through, I kept wondering if writing a one off utility might be faster. But it was possible to express variable structures, sizes and counts. I was using the syntax and the cmd line visualizer, but might have been more productive with their html/gui tooling.
Key shaped is not a bad term, probably moot, but it doesn't quite have the aspect-ratio I was thinking of - of course it also doesn't have the word "broken" in it either...
I too have a broken comb profile. Every now an then I get to have some fun and add or extend a few teeth. But for the most part the skills let me work through most tangles pretty well.
For cloud based storage, the LSM paper (w/ leveldb), and HDFS are good foundational references imho.
Obviously there are a lot of details beyond those areas, but understanding these are fairly short but will give you a basis to get much further to more cutting edge R&D discussions.
I don't know which it is or if multiple other factors are involved, but if you look at the structure of an eye, there are tissues which compose the iris which are connected to the adjacent tissue of where the lens is nestled. It's quite possible to me that increased use of the iris outdoors to close down and reduce light entering the eye could affect the "dynamic range" of the lens response to focal inputs - especially during the growth stages of kids.
This reminds me of archetypal idyllic images of ancient Greek education where a philosopher is teaching a group of students in an outdoor amphitheater. Maybe we need to redesign our schools to be outdoor, or at least with indoor structures with generous amounts of natural lighting.
I guess I think CD could still be valuable in that kind of setting in terms maintaining a deployment ready release that is ready to enter an externally imposed release cycle. (including delivering change mgmt artifacts etc...).
I don't think the utility had sent out any community notices. So when helis loiter around a little lower and slower than normal I think it's natural to be curious. Particularly when they show up on a daily basis for maybe a few weeks to a month.
I think the area is a lot more complex than the relative latency and throughput of synchronous vs async. For the observations in the environments of Ruby and Python, I think the observations feel true, but switching out to different sections of processing to different technologies I suspect different generalizations would have to be made.
I've thought about the same thing, but I suspect the main hurdle to overcome would be recognizing it as a data storage device in the first place. If one had an inkling of that use, then some future archeologist wouldn't need to know much about the electronics or controller. They might image the magnetic fields of the platters at 1000x the resolution and sensitivity of the drives original read/write electronics, then treat it like past archeologists might have treated a tablet with cuneiform.
If you have niche requirements then expect to pay some premium for the gear because the development costs are amortized into the unit price. It’s that way for AV gear as well as many other niches.
If the market won’t bear the price then people or companies able or willing to bear the development risk will shrink, or in this case maybe never develop.
Require video card PCIe passthrough and host the game on KVM? Take something like firecracker or some runt kernel, don't do a full system vm, just enough to run the game and anti-cheat?
Right now it's a bit more specialized to storage oriented server platforms that can run in the 10-40 NVMe devices. You get this sort of imbalance where any one or two high performance NVMe devices at full throughput can push more I/O than a single high end network link
There are a series of hardware updates and software bottlenecks to work through before access becomes more common, the performance will bubble up from below starting with more widespread NVMe devices, then faster NVMe over fabrics hardware will become more common, and drivers, hypervisors, filesystems, and storage apps will likely have to rethink things to re-optimize. That means different times in terms of showing up in the cloud/on-prem/etc.
I sometimes have to look at data structures in memory (not via a debugger) for systems, firmware, or embedded work. I wonder if it would be any good for that? Seems like a related capability to reverse engineering.
So the CRDTs could be applied to a document and an edit/change log to guarantee the consistency of the log and its entries, not necessarily the document itself?
Along those lines, seems you could design a far simpler, non-electric frame that could be rolled up a trunk with a mechanical cable/waldo cutter for the coconuts.
The assembly system is very nice. Once I learned you could enter variables and equations into most of the operations & constraint fields in OnShape, my ability to model in it became much better. It's great for placing multiple symmetric attachment points onto parts to construct assemblies for example.
I was in the same place you are, brushing up on CAD w/ a 3D printer. OnShape is a web based CAD service from some of the original technical creators Solidworks. I found that going through their tutorials helped a lot in understanding how the tools think.
Not open source like the other options discussed here, but free for hobbyists.