backlands

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 to appear in the profile).

> 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 I can read?

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 that was likely to cause harm, reckless disregard for safety, negligence, etc.

I think someone could argue (and many do) that inserting a piece of computer software (AI) in the middle lowers the level of intent and thus the level of responsibility, but having a particular type of software in the middle absolve one of responsibility seems unworkable and poor public policy.

> 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 to it as well as they fit in Rust or Java (for example). There are a bunch more constraining design choices they list further down:

> - Nothing ever moves

> - ... A string, an array of strings, a record with variable-size fields and an array of those records are each one contiguous block with no pointer in it

I'll have to look a bit deeper to decide if it's feasible to write many things in this language.