Comment on Everyday, as an American
linja@lemmy.world 3 weeks agoExcept no because the digits themselves are still big-endian. That’s nUxi.
Comment on Everyday, as an American
linja@lemmy.world 3 weeks agoExcept no because the digits themselves are still big-endian. That’s nUxi.
uis@lemm.ee 3 weeks ago
Mixed-endian. Or how I call it - abomination-endian.
linja@lemmy.world 3 weeks ago
Right, and the most significant bit of the whole date is the first Y in YYYY, which we can’t put at the end unless we reverse the year itself. So we can either have pure big-endian, or PDP-endian. I know which one I’m picking.
Your literal statement is also just wrong. The solitary implication of endianness is byte ordering, because individual bits in a byte have no ordering in memory. Every single one has the exact same address; they have significance order, but that’s entirely orthogonal to memory. Hex readouts order nybbles on the same axis as memory so as not to require 256 visually distinct digits and because they only have two axes; that’s a visual artefact, and reflects nothing about the state of memory itself. ISO 8601 on the other hand is a visual representation, so digit and field ordering are in fact the same axis.
uis@lemm.ee 3 weeks ago
We are talking about transferring data, not storing it. For example SPI allows both for LSB-first and MSB-first. In date digit-number-date is like bit-byte-word.
linja@lemmy.world 3 weeks ago
Right, and in data transfer every byte can be placed in an absolute order relative to every other. And the digits within the respective fields are already big-endian (most significant digit first), so making the fields within the whole date little-endian is mixed-endian.
I have iterated this several times, so I worry there’s a fundamental miscommunication happening here.