@mcc in several ways - though not all - I would argue that documentation is the _only_ technology, in that it advances the state of the art of what is known, can be constructed, can be built upon, and can be abstracted and generalized.
Without documentation, a new invention is just a device: interesting, perhaps so much so that it sparks inspiration in someone else to understand it, but it goes little further than that until it is documented in a way intended to communicate its key insights.
V now supports 3 more architectures:
- loongarch64
- riscv32
- s390x (IBM Z)
I always find it a bit surprising that "looking up executables in PATH" isn't implemented in one central place (there are at least 3 implementations that I use regularly: in libc, my shell, in Go, and probably more that I don't know about)
it's a weird thing because there are actually many different implementations, but I think in general the implementations act similarly enough that you can pretend there's only 1 implementation, I've never actually run into a problem caused by this
CatSynth Pic: CoCo with massive modular 😻🎛 https://catsynth.com/2025/05/coco-with-massive-modular/ #CatsOfMastodon #eurorack #modular
Check it out. I just published TeleMessage Explorer: a new open source research tool https://micahflee.com/telemessage-explorer-a-new-open-source-research-tool/
"Much of the essence of building a program is in fact the debugging of the specification." — Fred Brooks