The thing about memory ownership is that it's intrinsic (not incidental) complexity on a physical computer. If you don't want GC, you need ownership.
Not all languages provide ownership tooling though (e.g. C). Following Rust's success I suspect we'll see more ownership tools. https://twitter.com/migueldeicaza/status/1103427307451035648
miniblog.
Related Posts
GNU Make defaults to a single worker, and newer build tools (e.g. ninja) default to the number of physical CPUs. I wish there was an option for 'leave me a little bit of my machine to do stuff'.
Make defaults to a single worker, and newer build tools (e.g. ninja) default to the number of physical CPUs.
I wish there was an option for 'leave me a little bit of my machine to do stuff'.
https://tigerbeetle.com/blog/2025-02-27-why-we-designed-tigerbeetles-docs-from-scratch/ has an interesting distinction between "physical" and "logical" hash of a tarball.
By storing the hash of the decompressed tarball contents (i.e. the logical hash), they can verify the validity of files without needing to keep the tarball around.
