0001 == 0001. But 0001 + 0001 does not necessarily end up being 00001. Do you see my point now? You're missing the forest for the trees. 2 things are being discussed, not the outcome. Transport and bits, at the same time, but as separate things. Another analogy in another comment was analog wires, also good, break that and the resistance changes etc etc etc.
This many comments for something so simple. Breathe and stop going out of your way to misunderstand me. Ironically exactly how this thread even started. You clearly understand the subject since you already explained floating point arithmetic.
I'll give it one last shot: The person being referred to as flat-earth level stupid mentions bits, while he should've mentioned transport. And not taking into account his lack of domain knowledge and using the wrong lingo to misunderstand him and calling him stupid when he is right, just not wording it correctly is the problem.
Except all of the transport-layer protocols before the DAC are working in digital logic and have checksums applied to them. A bit flip is going to be detected and corrected or the packet will be dropped and resent. So the transport isn't going to have any impact on the bits whatsoever (barring effects like a packet arriving too late to emit the sound on time).
My point is bits moving from point to point. Passing through my buggy function handling 64 bit numbers as 16 bits could be another example, and using transport in that sense is probably wrong and I'll have to discuss TCP and everything related.
My only point is that there are a million different ways data can change from point A to B, some expected (.1+.2 example) others unexpected. The more I explain the more I'm being downvoted and I don't really understand why it's so controversial.
Starting to believe it's a HN thing I'm unaware of, if someone tries to explain a misunderstanding troll him and misunderstand as much as possible.
Please explain? If the 1s and 0s are still in the same order, what data has been lost?