I like the idea.... but it's a very basic overview, and you still have to check the longer spec if you want to actually code anything... So it's a fun looking p

I like the idea.... but it's a very basic overview, and you still have to check the longer spec if you want to actually code anything... So it's a fun looking poster, but (for me personally) has nothing more than a "fun" value take for example BMP: https://raw.githubusercontent.com/corkami/pics/master/binary/BMP.png https://raw.githubusercontent.com/corkami/pics/master/binary... Starts with a BM (two bytes).. ok File size, 0x42 but 4 bytes long.. so you have to both look at the image and the text on the right to see that you need to pad the length. a gap?? Data start.. ok, starts at 0x36, and indeed pixel data starts there.. but why is there a gap between the size and the data start? Is it mandatory or optional? Should it be zeros, or it doesn't matter? Header size.. 0x28.. ok.. so just the bitmap header, not the file header? from 0x0e onwards? Why is there a gap at the end? Should it be? Should it be padded to whatever random number it is? Width, height, ok... bpp ok. What is a nb plan? Image size.. 12? Bytes? Pixels? ... go count to see it's bytes Then pixel data.. ok 00 00 00 of padding, to pad to 0x41... why? How much padding should there be? Compare this to eg. this: https://en.wikipedia.org/wiki/BMP_file_format#Bitmap_file_header https://en.wikipedia.org/wiki/BMP_file_format#Bitmap_file_he... Offsets, sizes and explanaition of possible values. Also the gaps are explained ("Reserved; actual value depends on the application that creates the image, if created manually can be 0") Just taking the explanation from the example would explain more: https://en.wikipedia.org/wiki/BMP_file_format#Example_1 https://en.wikipedia.org/wiki/BMP_file_format#Example_1 <- this example is much more usable (if transformed to a poster format) for me personally. (yes yes, i'm nitpicking, but the poster just made me google stuff, that should already be on the poster)