The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: a.phillip.garcia@gmail.com (A. P. Garcia)
Subject: [TUHS] dmr note on BSD's sins
Date: Fri, 5 May 2017 13:56:06 -0500	[thread overview]
Message-ID: <CAFCBnZv6QEcmGfvdnLnwC9OWsbzwc6jVanYp6uYXoTZ=UguUAw@mail.gmail.com> (raw)
In-Reply-To: <1493992915.3765984.966912328.38F55A2B@webmail.messagingengine.com>

On Fri, May 5, 2017 at 9:01 AM, Random832 <random832 at fastmail.com> wrote:
> On Thu, May 4, 2017, at 19:14, Larry McVoy wrote:
>> On Thu, May 04, 2017 at 03:59:22PM +0100, Tim Bradshaw wrote:
>> > On 3 May 2017, at 14:41, Nemo <cym224 at gmail.com> wrote:
>> > >
>> > > Along these lines, who said "Cat went to Berkely, came back waving flags."
>> >
>> > And anyone who lived through the SunOS 4 -- SunOS 5 transition will know that some of those Berkeley flags (not specifically for cat, but almost certainly including those for cat) were really quite useful.  I remember spending really a long time finding and building BSD/GNU versions of utilities which actually had the options you needed on early SunOS 5 machines: later on Sun themselves put some of them back.
>
> I mean, there's a legitimate argument that some of them would have been
> just as useful or more as separate utilities than as flags. But to some
> extent the fully generalized version seems questionable.
>
> I mean, to apply the design philosophy to, say, ls -t (nevermind that
> this particular flag has in fact existed since Unix V1, it's exactly the
> *kind* of thing that should prompt someone who is consistently applying
> Pike's idea of the unix philosophy to say "sorting should be the sort
> tool"), you would have to have A) a basic "ls" command which does all
> the filesystem-accessing work and prints timestamps and all other
> relevant output in a format that can be sorted lexicographically, B) run
> it through sort(1), C) a command [or maybe an awk script] that will pare
> it back down to the usual human-readable formats (names only, ls -l, or
> maybe a timestamp-and-name format, with human-friendly timestamps). And
> then D) another tool to sort it into columns.

have you been using powershell lately? it makes things like this
rather enjoyable. yes, powershell is open source, and yes, it's been
ported to linux, but i think unix needs its own home-grown "object
oriented shell".


<snip>


  reply	other threads:[~2017-05-05 18:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 13:41 Nemo
2017-05-03 22:18 ` Dave Horsfall
2017-05-04 14:59 ` Tim Bradshaw
2017-05-04 23:14   ` Larry McVoy
2017-05-05 14:01     ` Random832
2017-05-05 18:56       ` A. P. Garcia [this message]
2017-05-05 17:33     ` Tim Bradshaw
  -- strict thread matches above, loose matches on Subject: below --
2017-05-03  0:52 Doug McIlroy
2017-05-03  0:59 ` Dave Horsfall
2017-05-03 12:54   ` Dan Cross
2017-05-03 13:09     ` Arthur Krewat
2017-05-03 13:46   ` Michael Kjörling
2017-05-03 14:57   ` Clem Cole
2017-05-03 15:34     ` arnold
2017-05-03 15:44       ` Clem Cole
2017-05-01 17:25 ron minnich
2017-05-01 18:09 ` Toby Thain
2017-05-02 16:11   ` Steve Johnson
2017-05-02 16:39     ` Erik E. Fair
2017-05-02 16:43       ` ron minnich
2017-05-02 20:28     ` Diomidis Spinellis
     [not found]       ` <CAM4FNStH7KH6+ab0o_fYKfzutvPQ__0w0Zq5_6hk4AFP=+aSAw@mail.gmail.com>
2017-05-02 20:34         ` Daniel Camolês
2017-05-02 20:34       ` Steve Johnson
2017-05-02 21:22       ` Andy Kosela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFCBnZv6QEcmGfvdnLnwC9OWsbzwc6jVanYp6uYXoTZ=UguUAw@mail.gmail.com' \
    --to=a.phillip.garcia@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).