as you say, the other thing is: what is “correct” today won’t necessarily be “correct” tomorrow if it takes 2x or 3x to get to the next iteration then what’s

as you say, the other thing is: what is “correct” today won’t necessarily be “correct” tomorrow if it takes 2x or 3x to get to the next iteration then what’s the point... (again, assuming we aren’t talking pacemakers etc) just my feeling, but these low level languages that try to have it both ways (working in the bit/byte realms, but also super high correctness) aren’t suitable for the realm of high iteration.... instead some high level language amenable to rapid iteration but still have high reliability should instead be built on top of something like rust but not necessarily _in_ it... [edit] forgot to mention parent post