> QEMU uses macOS hardware virtualization for the ARM64 desktop.
Huh, since when does QEMU support hardware virtualization on Apple Silicon? To the best of my knowledge, among all the VM managers available on macOS (VMware, Parallels, VirtualBox, …) only UTM currently supports hardware virtualization and that's through the Apple Virtualization backend, not through QEMU.
One could also phrase this principle in terms of entropy (in the information-theoretic sense): If I read some code and come across filter() and map(), I already have a pretty good idea of what the code is doing, without even looking at the filter criterion or the mapping function. Entropy is low. (There's only so many filter and map functions you could write for any given type or pair of types.)
Meanwhile, if I see reduce(), "anything" could happen. (Well, of course not anything but the set of possible reducers is surely much larger.) So entropy is high.
Avoid high-entropy constructs in your code. Try to keep entropy as low as possible. (For the same reason, code with a principled approach regarding side effects is a lot better than code where any function could mutate global state at any given time.)
Agreed! Many people are saying AI isn't really intelligent yet because it can't come up with genuinely new things. Maybe finding a rigorous formulation of QFT / high-energy physics would be a great test for whether they are!
> The “urine-no,” a hostile antiurination surface:
> Instead of minimising splash, it can instead be maximized by setting […], see Fig. 7a. Although not suitable as a commonly practical urinal, it showcases the design philosophy. Such a surface could be installed outdoors to deter public urination as the offender would fall prey to enhanced splash-back. This hostile surface may be dubbed as “urine-no,” as shown in Fig. 7b.
I spent this past weekend giving UTM w/ Apple Virtualization a shot and can confirm that it really does work fantastically well! The only downside seems to be that it's not possible to pass USB devices through to the VM guest yet?
reply