Well done. I recently revived the BadRAM kernel patch in order to do something similar; memtest86+ supports that functionality too, using
<F4>
,<F4>
,<F10>
,<F10>
."Computational Public Space" - Bret Victor
I don't like notebooks.- Joel Grus (Allen Institute for Artificial Intelligence)
rpypkgs: A Nix flake for RPython interpreters
Positive Affirmations for Site Reliability Engineers
The Tech Industry Doesn’t Understand Consent - Dhole Moments
µKanren: a minimal functional core for relational programming (2013)
Colored Functions and Monadic Effects (2022)
You always need to read what the machine generated for you; the machine can only write code for you, not understand code for you. Here, the biggest issue is that
copymight not work if the input and output containers are different, if the input has multiple framerates or audio tracks, etc.