Comments by "" (@grokitall) on "ThePrimeTime" channel.

This is just another case of the diamond dependency problem seen with objects, and should be solved the same way. Make the base abi definitions include semantic versioning info, and resolve it at link time or load time. If it cannot be resolved at that time, don't let the code run. C has always been defined as a source portable language, not an abi portable language, but some system and low level library developers don't help.
1
@shkhamd partly it is mandatory safety paranoia, but in more general programming if you make sure you check the parameters at the start, you don't need the checking in the sub modules to be as strict, as you know it is engineered to not pass down garbage which you will then have to deal with later.
1
the probe was one of the voyagers and was designed to last 5 years, still going strong 45 years later. dave farley looked at this study, and found it to mostly be biased bull designed to create talking points to help sell the book, just before it was released.
1
Having to start unit testing legacy code looks like it costs productivity, as it shifts your regression testing to the front of the process, but if you ensure that new code has tests, you gradually pick up speed until you are going faster than you would have before. Your only other option in this case is to refuse to test and end up with snowflake code nobody wants to touch, which will eventually break anyway at which point you are trying to fix it during an emergency. I would rather melt the snowflake a piece at a time until it is gone, resulting in any breakage either being covered by tests, or in a much smaller snowflake.
1
Because zig is expected to stabilise soon. Rust is even worse, as some code will not even compile properly without the nightly build ofmthe compiler chain. Sometimes those problems rule the language out of consideration.
1