Fwiw, as far as I'm aware, the principles and priorities outlined in the referenced article [1] were core Rust principles from the early days while it was still

Fwiw, as far as I'm aware, the principles and priorities outlined in the referenced article [1] were core Rust principles from the early days while it was still a project at Mozilla, rather than anything Amazon has defined recently. They may have become more formalized over time, into a sort "Six laws of Rustbotics" sort of thing. Eg.: - First Law: “Reliable: If it compiles, it works.” - Second Law: “Performant: Idiomatic code runs efficiently, except where doing so conflicts with the First Law.” etc. The crux of it all is prioritizing reliability and deterministic elimination of undefined behaviors above all other priorities. Only a handful of languages have done that in the past (Ada, Haskell, etc), but none reached mainstream acceptance in the way that Rust has. That is something new. I'm not aware of that particular value being closely associated with Amazon, moreso than Google or any other US Big Tech company. If not for Steve's concerns here, I would have guessed the opposite, that Rust is defining Amazon's engineering culture and principles, than the other way around. But it also sounds like Steve is being the canary in the coalmine here, and calling out something that may not be a huge problem right now, but could become so in the foreseeable future, and implicitly calling for governance reform similar to other communities [2] to prevent it. An ounce of prevention now is worth a pound of cure later. [1]:https://www.infoworld.com/article/3633002/the-future-of-rust.html https://www.infoworld.com/article/3633002/the-future-of-rust... [2]:https://news.ycombinator.com/item?id=28514002 https://news.ycombinator.com/item?id=28514002