There's a wide gulf between "one-off afternoon-long project done for fun" and "serving all traffic for amazon.com during black friday", so I am receptive to the

There's a wide gulf between "one-off afternoon-long project done for fun" and "serving all traffic for amazon.com during black friday", so I am receptive to the "I can just do this one off thing in Perl". On the other hand I know that once you get familiar with Rust it can be very productive (the "it hurts when I do that" stops when you learn to preemptively "don't do that" and stop fearing "this code is inefficient because it has two extra allocations!!!1") and I've seen too many "weekend projects" become the backbone of large enterprises. Rust's superpower is being able to scale up and down. But the GP might be talking about a project that falls squarely on the former. Anything that starts to move towards the later, I would immediately push for a language/ecosystem more tuned for "maintainability" than "time to first char on screen".