Similarly, translating from html/QML or js/py/rust is handy.
Its still a pain because even good models like opus are hit or miss. The code still has to be reviewed and adapted. Can save time though.
They are also very useful for mocking up a quick proof of concept.
Is X doable? Will Y potentially solve the problems that my clients need me to solve? mock it up in two seconds with a few prompts and a language model and you don't have to take a stroll down a garden path.
The actual work I still have to do but that's why I'm paid to do it.
Memory safe languages that are not garbage collected are not all that common. Ada and Rust are two examples.
With great care C++ and zig can be.
I'm sure there's a good reason a lot of the big players and the community at large have picked up rust though. Docs, error messages, cargo community etc.
I would argue that Rust does bring a lot to the table. I certainly would never code in C for work but I'll happily reach for Rust.