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.
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.
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.
41 replies
Megabyte:
Gigabyte:
Terrabyte:
Petabyte
Looks more like a panTerabyte
"some sort of elaborate Peta-bite image"
I wouldn't suggest petting that bite. It'll take a chunk.
Now I get it!
"I am never gonna financially recover from this."
Joe predicted the AI memory crisis. Mind blown!
You rang?
Oh hi there! 😆
3 year old account and now is when you decide to introduce yourself?
Nice to meet you
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.
Now I wanna see an animated Beetlejuice/Addams Family crossover
Word:-)
Funny, in Finnish a byte is called a syllable. Which would better apply to a nibble I guess.
A word is typically 4 bytes
https://en.wikipedia.org/wiki/Word_(computer_architecture)
It depends on the architecture. Some chips have weird words, like the Voyager spacecraft computer.
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.
Well technically
https://en.wikipedia.org/wiki/Syllable_(computing)
Trust Finns to hang on to some outdated term!
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.
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.
Memes can't even teach me about programming my voyager properly. Smh my head.
🤔 what's a
nibblethen? ... oh, it's half a byteI thought it was spelled 'nybble'?
According to the article linked both are valid
Yeah, I've always used the "nybble" spelling for data instead of tooth activity. But, also I think more people just use "hex digit".
Depends on if its referring to hard drive storage or reality.
Hard drive storage: 3.737965139 bits
Wtf is a nibble?
Half of a byte
What's the other half called?
jeremy
Wait until you learn what the other seven parts of a byte are called when the first one is called a bit.
One is called high nibble, the other half is called low nibble
Sounds like a case for the beauty doc
Ellbin
Two crumbs...
That bite looks like it was painful.₍^. .^₎Ⳋ