From: Jon Steinhart <jon@fourwinds.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Tech Sq elevator (Was: screen editors)
Date: Sun, 12 Jan 2020 13:47:44 -0800 [thread overview]
Message-ID: <202001122147.00CLligX584670@darkstar.fourwinds.com> (raw)
In-Reply-To: <20200112214152.9824C156E42D@mail.bitblocks.com>
Bakul Shah writes:
> On Sun, 12 Jan 2020 12:44:30 -0800 Jon Steinhart <jon@fourwinds.com> wrote:
> >
> > I wasn't being snarky. You said
> >
> > "The output is seen as truth because the representation is for some
> > reason too hard to get at or too hard to cascade through the system."
> >
> > I honestly have no idea what that means.
> >
> > Likewise,
> >
> > "There's a total comedy of work going on in the unix way of
> > a wc pipeline versus calling a length function on a list."
> >
> > I just don't know what you mean.
>
> May be this is not what Kevin meant but the way I interpreted
> his message: smushing everything down to strings for output as
> in unix pipelines loses any underlying structure which then
> may have to be rediscovered by the next program in the
> pipeline by parsing. This is slower, indirect and errorprone.
> If one can communicate a structured representation of data between
> components that would be better.
Ah. So lines IS the structure that a lot of people want. As I just
said in a post, the JSON tools are a good example of communicating
structured data although I would have done them differently.
Jon
next prev parent reply other threads:[~2020-01-12 21:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 13:43 Doug McIlroy
2020-01-12 16:56 ` Warner Losh
2020-01-12 17:21 ` markus schnalke
2020-01-12 20:25 ` Kevin Bowling
2020-01-12 20:32 ` Larry McVoy
2020-01-12 20:34 ` Jon Steinhart
2020-01-12 20:40 ` Kevin Bowling
2020-01-12 20:44 ` Jon Steinhart
2020-01-12 21:03 ` Kevin Bowling
2020-01-12 21:37 ` [TUHS] Tech Sq elevator (Was: screen editors) [ really I think efficiency now ] Jon Steinhart
[not found] ` <CAEoi9W4fXLaTRM1mv4wnVbifCFBEw_iKL9cds8ds-FBRTwM-=g@mail.gmail.com>
[not found] ` <CAEoi9W6LedGGjWPO=ZgZzVdGLqs8drhqcWkvA_DfKTOtMDgegQ@mail.gmail.com>
2020-01-13 23:46 ` Dan Cross
2020-01-14 23:17 ` Kevin Bowling
2020-01-18 15:45 ` Michael Parson
2020-01-18 18:45 ` Jon Steinhart
2020-01-18 18:59 ` Michael Parson
2020-01-18 20:31 ` Adam Thornton
2020-01-21 21:57 ` Derek Fawcus
2020-01-22 7:21 ` arnold
2020-01-22 7:29 ` Tyler Adams
2020-01-12 21:41 ` [TUHS] Tech Sq elevator (Was: screen editors) Bakul Shah
2020-01-12 21:47 ` Jon Steinhart [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-12 22:25 Doug McIlroy
2020-01-12 22:40 ` Kevin Bowling
2020-01-10 17:27 Noel Chiappa
2020-01-10 20:18 ` Angelo Papenhoff
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=202001122147.00CLligX584670@darkstar.fourwinds.com \
--to=jon@fourwinds.com \
--cc=tuhs@tuhs.org \
/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).