setheron

proposed by John Ericsson (Nix core contributor) for the idea of Null namespaces to make namespaces cheaper for when doing finegrained sandboxed builds.

What about the cyborgs ? Whatever their name was.... I can't remember. But they were the "thinking machine" class?

The kernel's RNG is seeded from a seed passed at boot.

You can ask for as many schedules as you need `rewind check --all --schedules 3000` (for 1 in 1_000 lets say) but the code also pushes the scheduler toward bad timing: it switches threads at random points and sometimes stalls a process for up to about a millisecond, the way a busy CI machine would.

Code models and linking of objects.

We can work on harder problems at the frontier of the models knowledge. I'm working on one such domain, and I find AI use helpful, but I still need to be incredibly astute.

Stuck feeling it's so cool and also so complicated.

I like your phrasing; I think too often we get caught trying to optimize for everything.

For my own edification I often let performance & size slip to see if I can re-imagine something simpler from the start from a complete new direction;

This is often the greenfield hubris because it doesn't have all the same battle-scars of the full implementation so I try to make sure I take a very different approach to make it worthwhile :)

Then I just have faith that performance and size can always be improved over time.

I won't share any feedback specially but choosing low level primitives as research I found challenging due to the unfamiliarty in peer review circles.

I enjoyed all the papers I read on my graduate classes that bordered on "art" whereas now they seem to be obsessed with performance only.