One could actually have both. Spiral provides a lot of its performance by correctly specifying error constraints, which is a form of safety. You could specify a

One could actually have both. Spiral provides a lot of its performance by correctly specifying error constraints, which is a form of safety. You could specify architectural constraints by hand too, for performance and portability. (With some good defaults.) One could technically also get memory and reference safety this way. Which is the opposite of what Rust does for example, where it defaults to do a particular model of referencing memory and makes using any other painful. It also does not have any constraints on timing or redundancy if necessary. Automate some of this handling but still keep it explicit and you have a potential winner.