3 ms·
BE is still common in very resource constrained applications like microcontrollers. You know, applications where having to do endianess swap actually has a sign
by audunw 4y ago
BE is still common in very resource constrained applications like microcontrollers. You know, applications where having to do endianess swap actually has a significant impact? Applications where it might actually make sense to use this kind of codec?
I was really thankful that Doom WAD file was big endian (side effect of being developed on NeXT?) when I ported doom to an nRF microcontroller.
- hcs 4y agoIf you're exporting assets for a game, and the swap would be significant, shouldn't it really be generating big or little endian depending on the target? Many audio engines do this, using e.g. RIFX on big endian targets and RIFF on little.
- pluijzer 4y agoI believe that in the case with Doom, and many other games that released there code as open source; the game assets are not in public domain and remain closed.
- kstenerud 4y agoIsn't endianness either little or selectable on most (if not all) microcontrollers these days? For example https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.3.pdf https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.3.pdf is little endian. Considering that little endian is objectively better for more types of data structures than big endian is [1], one would expect things to eventually converge on little endian (barring the entrenched big endian network protocols that hold everything back). Building for the eventuality of little endian would make more sense in a modern format. [1] https://www.technicalsourcery.net/posts/on-endianness/ https://www.technicalsourcery.net/posts/on-endianness/