Nibbles are still a thing in embedded programming and in ultra low bandwidth comms like LoRa. For example you can pack 2 BCD digits into a byte, one for the high nibble and one for the low nibble. This results in the hex representation of the byte actually being directly readable as the two digits, which is convenient.
Datasheet for sensors will sometimes reference nibbles as well, often for status bits on protocols like Onewire where every bit counts. i.e low nibble contains a state value 0-15 and high nibble contains individual alarm flags.
QBasic came with NIBBLES.BAS, a snake game using text-mode characters as “pixels”. Specifically it faked a 80x50 “pixel” grid using the standard 80x25 text screen where each 8-bit (=1 byte) text character made up two monochrome pixels using ▄ or ▀ or █ or an empty space.
I assume the name derived from the fact that, in a way, one pixel was “using half a byte”, i. e. a nibble.
Nibbles are still a thing in embedded programming and in ultra low bandwidth comms like LoRa. For example you can pack 2 BCD digits into a byte, one for the high nibble and one for the low nibble. This results in the hex representation of the byte actually being directly readable as the two digits, which is convenient.
Datasheet for sensors will sometimes reference nibbles as well, often for status bits on protocols like Onewire where every bit counts. i.e low nibble contains a state value 0-15 and high nibble contains individual alarm flags.
QBasic came with NIBBLES.BAS, a snake game using text-mode characters as “pixels”. Specifically it faked a 80x50 “pixel” grid using the standard 80x25 text screen where each 8-bit (=1 byte) text character made up two monochrome pixels using ▄ or ▀ or █ or an empty space.
I assume the name derived from the fact that, in a way, one pixel was “using half a byte”, i. e. a nibble.
Nibbles can also be used with image types that are less than 8-bit