I think the failures like this one, deleting files, etc, are mostly unrelated to the programming language, but rather the llm has a bunch of bash scripting in its training data, and it'll use that bash scripting when it runs into errors that commonly are near to bash scripting online... which is to say, basically all errors in all languages.
I think the other really dangerous failure of vibe coding is if the llm does something like:
cargo add hallucinated-name-crate
cargo build
In rust, doing that is enough to own you. If someone is squatting on that name, they now have arbitrary access to your machine since 'build.rs' runs arbitrary code during 'build'. Ditto for 'npm install'.I don't really think rust's memory safety or lifetimes are going to make any difference in terms of LLM safety.
So yeah, I must narrow my Rust shilling to just the programming piece. I concede that it doesn't protect in other operations of development.
That's very specific of Python. A few years ago we were multiplying a lot of matrices in Fortran and we tried to transpose one of the matrices before the multiplication. With -o0 it was a huge difference because the calculation used contiguous numbers and was more chache friendly. Anyway, with -o3 the compiler made some trick that made the difference disappear, but I never tried to understand what the compiler was doing.
I specialize in computer networking in my day job. Most of what I do is Cisco routers, Cisco switches, and Cisco firewalls. I would be interested in learning more about cellular networks. I haven't put any effort into exploring this for myself. If there is a track similar to CCNA → CCNP → CCIE then it isn't well-known (well, not known to me).
>human curation will be a selling point
Look at the success of TikTok. Automated recommendations enabled it to become one of the top apps in existence. There is not evidence that consumers care who curated the content. The quality of the recommendation is experimentally proven to be much much more important.