I've seen programs that end up swapping bytes two, three, even four
times as layers of software grapple over byte order. In fact,
byte-swapping is the surest indicator the programmer doesn't
understand how byte order works.
Try to imagine yourself in the IPMC, being asked to vote for the release of
[Apache OpenOffice] 3.4. You want to make sure the release follows Apache
guidelines. You want to protect the ASF. You want to ensure that users,
including developers using our source code packages, get the greatest
benefit from the release. But you are faced with a 10 million line code
project, larger and more complex than anything you've faced before at
What do you do? Where do you start?
Honestly, I have absolutely no idea.
-- Rob Weir
Regular ls output, tuned as it was for 9600 baud terminals or so,
is really too verbose for modern media such as twitter and cell
phones. This new output format, enabled by the -j switch (or
--format=jam, but you don't want to type all that on a cell
phone!), brings ls into the 21st century with an appropriate level
to post comments)