this post was submitted on 06 Jun 2024
1263 points (96.6% liked)
Lemmy Shitpost
26958 readers
3291 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Conversion is always extra step, but you don't need it if you use same timezone as other participant.
Big-endian is big. Alternatively DD.MM.YYYY or DD.MM.YY for little-endian lovers.
Except no because the digits themselves are still big-endian. That's nUxi.
It's more along the lines of most signigicant bit/least significant bit, rather then byte order.
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.
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.
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.
big-endian (most significant byte or in our case number first).
Digit in base2 is bit. Endianess is byte order, not bit order. MSb-first is bit order.
Ok, I think I see the problem. To me, MSb (Most Significant bit) isn't an ordering at all, just a label that one particular bit has. To specify an ordering, you'd also need to say whether that bit comes first or last. This concept doesn't exist in computer memory because, as previously mentioned, bits in a byte aren't ordered in memory. I was thinking of the individual digits in a field (each Y in YYYY) as separate bytes in a word, so endianness order makes sense to think about; separate fields in this analogy were contiguous like struct fields. I think my mental model is sensible, since ISO 8601 is fundamentally a sequence of characters, which are all in an absolute order.
Yes. And it starts to exist when transferring data over serial connection. SPI, USB, you name it.