Crossposted from https://programming.dev/post/56336053

nyaaa bytes you

all 3 comments

sorted by: hot top controversial new old
[–] 7 points 1 month ago

Himbxsadecimal

  • source
  • [–] 6 points 1 month ago

    I'd hate to see a kilobyte. Let alone a megabyte or gigabyte or terabyte or...

  • source
  • [–] 4 points 1 month ago

    What about word, doubleword, quadword? (though some naming conventions use halfword for 16 bit and word for 32 bit)

  • source
  • 39 comments in c/programmer_humor@programming.dev view that post
    [–] 135 points 2 months ago* (6 children)
  • [–] 46 points 2 months ago (5 children)
  • [–] 7 points 1 month ago (2 children)

    3 year old account and now is when you decide to introduce yourself?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 month ago (1 child)
  • [–] 4 points 1 month ago*

    Ya know, when I first made that comment all I did was a quick check on your profile and saw no data;

    But then I realized my instance is only a month or so old so perhaps I’m missing data, and Lo and behold I was correct, I just figured it was a 3yo account with absolutely no activity coming back to life, I retract my previous comment.

  • source
  • parent
  • [–] 13 points 2 months ago (8 children)
  • [–] 5 points 2 months ago (6 children)

    Funny, in Finnish a byte is called a syllable. Which would better apply to a nibble I guess.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 2 months ago* (5 children)
  • [–] 5 points 1 month ago (3 children)

    Oh. Shit, first I didn't know what a nibble is, now I didn't know what a word is ... I'll just show myself out and make sure I never try to write any assembler code.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 month ago

    Actually that does sound best... but not because of anything to do with you, that advice just applies to all humans for the last basically twenty years. So it's nothing to do with AI slop, but rather compilation got SO FREAKING GREAT that in like 99.9% of cases it does better than a human.

    Ironically, one of the reasons for that is that concepts like "word" varies between different architectures (like like "byte" too - e.g. you've likely heard the distinction between 32-bit vs. 64-bit systems). As the other person said it is usually 4 bytes but other times it can be like 2 (in super old systems I suppose) or more than 4 in like super powerful ones (128-bit ones maybe?).

    And compilers keep track of ALL of those minutiae, as well as a bunch more stuff too. Like a small(-ish) loop that only runs a couple to few times is far more efficient to just be duplicated in the assembly code, rather than have the GO-TO procedure jump back to its beginning spot. And also it helps immensely to feed things to the chip based on what the various cache sizes are - L1, L2, L3 (though not all chips have all... or even any of those).

    So yeah, it's best to leave compilation to the computer to handle, thus freeing up the programmer to handle the overall logical flow and deal with other higher-order effects like code reuse and documentation and stuff.

  • source
  • parent
  • [–] 7 points 1 month ago* (1 child)

    Word=4bytes Dword=8bytes=2words Qword=16bytes=4words

    *On a 32-bit, x86 arch. The word size on Voyager is like 12-bits or something odd.

  • source
  • hideshow 1 child comment
  • [–] 11 points 2 months ago (5 children)

    🤔 what's a nibble then? ... oh, it's half a byte

  • source
  • hideshow 5 child comments
  • [–] 8 points 2 months ago (4 children)

    I thought it was spelled 'nybble'?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 2 months ago (8 children)
  • [–] 9 points 2 months ago (6 children)
  • [–] 10 points 2 months ago (5 children)

    What's the other half called?

  • source
  • parent
  • hideshow 5 child comments