No, it’s the other way around. Write everything in a safe language so that you don’t have to worry too much about crashes and other problems, but choose a langu

No, it’s the other way around. Write everything in a safe language so that you don’t have to worry too much about crashes and other problems, but choose a language that is _fast to write_ for your first attempt. When you write that first program you will not know all of the answers yet, or even all of the questions. You want to explore the space of possible solutions quickly and efficiently, so a dynamic language like Javascript (or Lisp, Python, whatever) is the best choice. Later once you have figured out how the program should be written, that’s when you go back and rewrite it in a language that is _fast to run_, like Rust. Sure, if you had written it in Rust to start with it would have been fast to start with. The problem is that the exploration would have been far slower, taking years instead of months. And because you haven’t done the exploration, it is unlikely that you will start with the right architecture. That means a lot of factoring and refactoring once you figure out what the right architecture is. In most cases you can gain far more by writing the program quickly than you can by writing a quick program.