It's fascinating that older lisps let you adjust the load factor in hash maps yet few newer languages expose this setting. For example, Rust doesn't have it yet: https://github.com/rust-lang/rust/blob/70073ec61d0d56bca45b9bd40659bb75799cd273/src/libstd/collections/hash/map.rs#L121-L124
Related Posts
It's odd how lazy evaluation is generally seen as a niche design choice, yet the vast majority of languages treat `foo() || bar()` as short-circuiting.
It's always seemed odd to me that the Rust stdlib is so lean (no random numbers, regex, HTTP) yet clippy is so big (correctness, performance, style preferences, even 'too many arguments').
Maybe it's because cargo is mature but clippy doesn't have an extension ecosystem?
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.