In Jai it is easy to, for example, have bounds checks on during the entire development process to aid in finding bugs, then turn off bounds checks in a dozen critical loops for testing and release, then turn bounds checking on in one loop that still proved crash-y.<p>Blow has said many times: he doesn&#x27;t think the language should be prevent you from shooting yourself in the foot, because sometimes that means preventing you from doing what you want to do.<p>He usually asks: what is something simple we can do that will give us 90% of the benefit, without adding a layer of overhead. Rather than Rust&#x27;s &quot;Safe All The Things!&quot; approach, bounds checking is just another tool you can use or not use as is appropriate for the context.