Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

> No matter what, you are trusting a compiler vendor that the code it compiles and the functions it links against don't have bugs.

I guess the key factor about a standard is that as a corporation you can point fingers if something goes wrong ("the compiler and/or the MISRA C checking tools you sold me are not compliant with the standard because of this bug!").

Also the committee can point fingers back if required ("the UB is clearly specified in the standard!").

If I were a team manager at a big automotive factory in charge of the ECU system, I would go the private way, with guarantees, and paying a lot of money. In case of failures, I can point fingers and someone would answer the phone on the other side if I complain.

Who should I call or who should I point my finger at, if something goes wrong because of a bug in Rust? A Github user on the other side of the planet?



If there were a standard, you'd still be pointing at opposite-hemisphere github users. This is what I mean about the streetlight effect - the standard has jack to do with the outcome. If you are buying a product from a vendor, the vendor is responsible for the product, and if you are using an open-source community-managed product, it's much harder to point fingers. The source of truth can be an ISO standard, or it can be documentation, it doesn't matter.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: