But i think this is apples and oranges - C maps pointers and memory allocation in a very direct robust manner, even Python allows you to dis back to see the stack.
But this hard-line-to-underlying reality is unlikely to exist looking at how this months k8s will configure last years AWS route53.
It just works 80% of the time is a disaster, 98% of the time might be bearable. is it above 99%?
Indeed, my point was that it's a quantitative question not a qualitative one.
When compilers created buggy code every other day, when memory allocators were unreliable because memory fragmentation would make it likely for new allocations to fail in the lifetime of a normal program execution, etc, it would be, as you said "a disaster if it works <95%" of the times.
Did k8s reach 99%? The jury is still out. Probably not yet, but in principle I don't see anything wrong pursuing that path just because it's "another layer". We use abstraction layers all the time; they allowed progress (Yes often we went too far)
But this hard-line-to-underlying reality is unlikely to exist looking at how this months k8s will configure last years AWS route53.
It just works 80% of the time is a disaster, 98% of the time might be bearable. is it above 99%?