Conversation

Notices

1. Embed this notice
   ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Friday, 24-Oct-2025 09:32:14 JST ✧✦Catherine✦✧

   endianness is just a plot by big endian to sell more byte swap operations

   • Embed this notice
     Ted Mielczarek (tedmielczarek@mastodon.social)'s status on Friday, 24-Oct-2025 09:34:26 JST Ted Mielczarek

     in reply to

     @whitequark ironically with "network byte order" being defined as big endian, it's little endian systems that have wound up doing more byte swaps!

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Friday, 24-Oct-2025 09:37:00 JST ✧✦Catherine✦✧

     in reply to

     • Ted Mielczarek

     @tedmielczarek Big Endian has successfully lobbied to enshrine their corrupt influence in our sacred constitution!

   • Embed this notice
     Mike P (fentiger@mastodon.social)'s status on Saturday, 25-Oct-2025 03:24:43 JST Mike P

     in reply to

     @whitequark What we need is "USB endianness". Reverse the byte order, and it's still wrong, but if you reverse it again, it becomes correct.

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Friday, 31-Oct-2025 15:20:52 JST ✧✦Catherine✦✧

     in reply to

     • Reid :ablobcatattention:

     @Reiddragon most protocols designed in the last 20 years are little endian

   • Embed this notice
     Reid :ablobcatattention: (reiddragon@fedi.reimu.info)'s status on Friday, 31-Oct-2025 15:21:16 JST Reid :ablobcatattention:

     in reply to
     @whitequark except it's little endian that swaps shit
   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Friday, 31-Oct-2025 22:27:24 JST ✧✦Catherine✦✧

     in reply to

     • Reid :ablobcatattention:

     @Reiddragon touch grass

   • Embed this notice
     Reid :ablobcatattention: (reiddragon@fedi.reimu.info)'s status on Friday, 31-Oct-2025 22:27:38 JST Reid :ablobcatattention:

     in reply to

     • Reid :ablobcatattention:
     @whitequark Also, just think of how bitshifting works on a little endian machine.
     
     If I have 0xFF 0x00 in memory then shift the whole thing left by 4, it turns into 0xF0 0x0F. Like, wtf? Sure, in proglangs it doesn't affect things as much but that's just because shit gets constantly swapped in the backend to account for LE's insanity
   • Embed this notice
     Reid :ablobcatattention: (reiddragon@fedi.reimu.info)'s status on Friday, 31-Oct-2025 22:27:44 JST Reid :ablobcatattention:

     in reply to
     @whitequark all x86's fault. It doesn't even make sense!