The IETF QUIC working is well-aware of this, and is attempting to save design room for future QUIC versions as much as possible. The "QUIC invariants" spec documents everything that is guaranteed not to change, but other than than everything in a future QUICv2 could be updated (e.g. tls version, features, large parts of packet header layout).
Yeah but that's for the insurer. Getting "insurance insurance" would be for the customer, to protect getting screwed over by their original insurer, who has chosen the short-term option of rejecting a valid claim, but which results in long-term loss of trust in the entire industry. The only solution being...more insurance? Crazy.
Go only supports static linking. No dynamic linking means no linking issues when deploying the same binary across a billion machines in the Googleplex.
I think just like other languages, writing Rust leads to a familiarity with what the compiler wants. Then you spend more time thinking about design and the problem at hand, and less fighting the compiler. I think Rust will ultimately be easier than C++ to write because while there are tricky concepts to master, there should be much fewer of them than C++ has.