UNIX philosophy.

Why is the opposite of cat tee, and it's not even a proper opposite but also does a different thing (outputs to stdout) (which is ostensibly its real purpose)?

Also, why do I even need the opposite of cat (and cat itself while we are at it) when those needs should have been served by input and output redirection, but turns out that the latter is completely made up and broken shell bullshit: you can't cat <file1 <file2, and you can't EDITOR='echo zzz >>$1' visudo for example.

Orthogonal design, my ass. Do one thing and do it well, my ass.

>>36

Well, LAC is proposing an 8 bit storage format, and it's easy to show that 8 bits are not enough. you can try it out with a gradient in gimp and compare expansions to 8 and 16 bit. you can easily make out letterboxes in the former.

We all know PBM and it's capability of storing images in a non-binary format, but it has drawbacks as well, e.g., it doesn't compress well.

And if you think about it: How often are you going to look at the image data by hand? How often are you going to generate images in the command line? This is a rare use-case and in my opinion, the way to go is for the 99%, those who handle their everyday images and need a compact storage format.

I don't know why everbody gets so obsessed about endianness to be honest. If you don't understand it, you can just copy paste the code fragment "invert.c" from the farbfeld-page (tools.suckless.org/farbfeld) and immediately start coding an image filter. :)