I did some benchmarking, and while with some fio usage I can get the lock contention in btrfs to show up, with cargo+mbx builds the speed of zfs and btrfs seem comparable (and the lock contention doesn't actually seem…
> I use ZFS bc Btrfs has massive contention problems with concurrent Rust builds I haven't read about btrfs having issues with concurrent workloads like multiple concurrent rust builds. Are there notes on this somewhere…
People are held accountable for accidents (things they did but did not intend to do) all the time. That's why we have different crimes depending on whether or not there was: intent to do cause harm, intent to do a thing…
> Goose looks familiar like C or Rust, and is built on one idea: there is no heap So it looks like it restricts the memory management to 100% scope based. I expect that makes a lot of designs for programs not translate…
I did some benchmarking, and while with some fio usage I can get the lock contention in btrfs to show up, with cargo+mbx builds the speed of zfs and btrfs seem comparable (and the lock contention doesn't actually seem…
> I use ZFS bc Btrfs has massive contention problems with concurrent Rust builds I haven't read about btrfs having issues with concurrent workloads like multiple concurrent rust builds. Are there notes on this somewhere…
People are held accountable for accidents (things they did but did not intend to do) all the time. That's why we have different crimes depending on whether or not there was: intent to do cause harm, intent to do a thing…
> Goose looks familiar like C or Rust, and is built on one idea: there is no heap So it looks like it restricts the memory management to 100% scope based. I expect that makes a lot of designs for programs not translate…