<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 10, 2024 at 7:23 PM Nevin Liber <<a href="mailto:nliber@gmail.com">nliber@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Fri, May 10, 2024 at 11:37 AM Clem Cole <<a href="mailto:clemc@ccc.com" target="_blank">clemc@ccc.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><span style="color:rgb(0,0,255);font-family:arial,helvetica,sans-serif">The key is that not all "bloat" is the same (really)—or maybe one person's bloat is another person's preference.</span><br></div></div></div></blockquote><div><br></div><div>A lot of "bloat" comes because our systems really aren't focused on "discoverability".</div><div><br></div><div>While I probably have used "pr" in the past, I've totally forgotten, the name "pr" doesn't really help me understand what it is for, and it's just one of 982 files in my /usr/bin directory alone. How does one discover it?</div></div></div></blockquote><div><span class="gmail_default" style="font-family:arial,helvetica,sans-serif"><font color="#0000ff">Chapter 1, Page 15 of Kernigahan and Pike -- "The Unix Programming Environment" </font></span></div><div><span class="gmail_default" style="font-family:arial,helvetica,sans-serif"><font color="#0000ff"><br></font></span></div><div><span class="gmail_default" style="font-family:arial,helvetica,sans-serif"><font color="#0000ff">It's still the best book for learning, regardless if Linux is your preferred UNIX implementation.</font></span></div><div><font color="#0000ff"> </font></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>It's like using "sed" instead of "head": sure, if you already know "sed", you don't need "head", but for English speaking folks who know "tail" is there, it would be (and was in the old days) surprising and frustrating not to have "head".</div></div></div></blockquote><div><font color="#0000ff"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hmmm.. date on 1BSD tape for head is Nov 23, 1977. </span> <span class="gmail_default" style="font-family:arial,helvetica,sans-serif">It's been around since the Sixth Edition.</span></font></div><div><font color="#0000ff"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">And again - this is my observation - some tools are easier to use, and the head is easier than a sed script. One can argue a shell script that exec's sed for you would have been sufficient to Joy's program.</span></font></div><div><font color="#0000ff"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">However, in wnj's defense, he wrote it for sed was not part of the Sixth Edition.</span></font></div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>