farbfeld

farbfeld is a lossless image format which is easy to parse, pipe and
compress.
It has the following format:

| Bytes | Description |
|--------|------------------------------------------------------------|
| 8 | "farbfeld" magic value |
| 4 | 32-Bit BE unsigned integer (width) |
| 4 | 32-Bit BE unsigned integer (height) |
| [2222] | 4⋅16-Bit BE unsigned integers [RGBA] / pixel, row-aligned |

http://tools.suckless.org/farbfeld/

BE

Backwards-endian instead of logical endian? Idiot.

>>21

It's the network byte order. If this goes beyond your small head it's not my problem.

>>22
65535 is the max value of an unsigned 32-bit integer? u must be the 1 with small head m8

>>23
when does this 'network byte order' meme die?

>>28

Yeah, nvm, I meant 16-bit. You knew what I meant.

"Big-endian is the most common format in data networking; fields in the protocols of the Internet protocol suite, such as IPv4, IPv6, TCP, and UDP, are transmitted in big-endian order. For this reason, big-endian byte order is also referred to as network byte order."

In the end it doesn't matter which endianness you use. If I used LE for everything, I would still have to use the endianness-conversion-functions for the BE systems it may run on. The rest is cool. ;)

29

All valid points you made, no need to become insulting, else you'll notice people will stop talking to you.
YMMV of course, why so charged? Nobody is forcing you to use farbfeld anyway, so if you prefer another format, feel free to use it. Today alone I talked to 4 people who told me that they would've loved to have farbfeld in previous problematic situations. These people alone showed me that the time I spent on this was worth it. ;)

What projects are you working on at the moment?

>>23

network byte order

And? Why does that somehow make it better?

It doesn't. It's pure cargo-cult dogma, not justifiable by any other means.

BE:
Bit n has weight 2^x-n. Byte n has weight 256^x-n. You have to know how long the value is, x, because all the values shift depending on the length!

LE:
Bit n has weight 2ⁿ. Byte n has weight 256ⁿ. Simple and logical.

>>30

would still have to use the endianness-conversion-functions for the BE systems it may run on.

Who cares about BE systems anyway? The only ones that are of any importance are network equipment, and that's just because of the stupid choice made 20 years ago...

Ironically, Ethernet is LE bit order but BE byte order.

>>41
Written like a true cargo-cult mouthbreather.

>>48
But Cudder-sama, real life numbers are BE!

>>53
Real-life numbers are a Semitic invention, that's why they are written (in the natural order) from right to left. Since memory addresses grow from left to right (and from down to up) (and here I'm using the notion of growth similar to that of a fir, with new leaves or needles as it is appearing at the top, as opposed to say a bamboo where new plant matter appears at the bottom), with all that said it would be appropriate to use LE.

kinda don't like the BE thing, everyone is complaining about it. Would you consider changing that?