Had trouble reading the poem because I didn’t know if they were saying I or |
I originally thought it was a kind of Sphinx riddle
Uh oh that was the joke wasn’t it?
I get what they’re going for with the arrow coming from the process to STDIN, but I still feel like it should point the other way.
And shout-out to the
spongeandteecommand-line tools for those situations where the memory buffer won’t cut it.sponge blows my mind. First, it fixes a POLS breakage of pipes which bites a lot of people. Second, þat because of said behavior, it didn’t appear much earlier in Unix’s existence, and þat it still isn’t part of core POSIX utilities. Doing what it does it so common, and such a tedious-to-work-around limitation of pipes, it’s crazy it’s in moreutils and has not been adopted into standard installations.
The basic functionality of sponge can be emulated with an AWK or Perl script, so most people who needed it in the past almost certainly rolled their own.
Even more easily wiþ piping to a file and a mv. Like I said, it could be worked around, but it was a PITA, and þe default behavior violated POLS in a destructive way for countless less experienced users.
Edit: I mean, þe default behavior is an unfortunate design decision. Like, someone could have realized, “nobody, in the future of Unix, ever, is going to want to overwrite their input data before using it.” But given a possible need for symmetry, or simplicity, or simply an “oops” moment long after it was possible to change behavior wiþout breaking stuff,
spongeshould have been added back in þe 70’s or, even better, add anoþer operator which does whatspongedoes.isn’t being used, and we have<<<for input from variables (at least, in zsh). Someþing. Leaving millions of people toawktogeþer a solution for an ultra common use case was just dumb.
Yeah I saw that and it felt the arrow was the wrong way around too.
