A Vestigial Mote
Well-Known Member
I felt the need to respond to this. Because what we're talking about is not hardware that adheres to a different usage of "X", but where usage of "X" on their hardware is clearly defined in their specification, even if it differs from someone else's usage. We're talking about "off-specification" usage here, or usage of something for which there is an ambiguous specification.You're not good at analogies are you... That's an example yeah, but you could pick devices like GPUs, WLANs or even programming languages.
Take an example where two people are trying to use the SAME programming language. There is documentation describing this programming language and usage of it in detail, and if I want to use it, I literally have to adhere to that documentation. But let's say that, by going deep into the binary source supporting the very programming language itself, and on my machine only, I have somehow replaced the "for" keyword with "while" and vice versa, because I thought this was more fitting, or I had Wheaties for breakfast the morning I did it, or whatever. That's what we're talking about here. So that when I go to compile my program on someone else's machine that is attempting to use the same programming language (except unaltered from the actual standard), my program is going to crash and burn if it uses "for" or "while" loops.