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 12:44:30 -0800 [thread overview]
Message-ID: <202001122044.00CKiUNV573279@darkstar.fourwinds.com> (raw)
In-Reply-To: <CAK7dMtBhRNUS4t-CaUFnWAP7TWpLRetTA36pL5wP1q6=19APnQ@mail.gmail.com>
Kevin Bowling writes:
> I honestly can't tell if this is genius level snark :) in case you're
> sincere we generally go to great lengths to build up data types and
> structures (in C lingo) when programming only to tear those useful
> attributes off often at inopportune times. Basically type
> systems/type safety have been too expensive or too difficult to use
> through history.
>
> Think of sitting at an SQL prompt as a counterpoint. You can pretty
> easily get at the underlying representation and relationships of the
> data and the output is just a side effect. Not saying SQL is the
> ultimate answer, just that most people have a bit of experience with
> it and UNIX so can mentally compare the two for themselves and see the
> pros and cons to preserving the underlying representations.
>
> Regards,
> Kevin
>
> On Sun, Jan 12, 2020 at 1:34 PM Jon Steinhart <jon@fourwinds.com> wrote:
> >
> > Kevin Bowling writes:
> > > This is kind of illustrative of the '60s acid trip that perpetuates in
> > > programming "Everything's a string maaaaan". 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.
> > >
> > > 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. Nonetheless, the
> > > unix pipeline was and is often magnitude easier for a single user to
> > > get at. This kind of thing is amusing and endearing to me about our
> > > profession in modern day.
> > >
> > > Regards,
> > > Kevin
> >
> > Can you please elaborate? I read your post, and while I can see that it
> > contains English words I can't make any sense out of what you said.
> >
> > Thanks,
> > Jon
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.
Jon
next prev parent reply other threads:[~2020-01-12 20:44 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 [this message]
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
-- 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=202001122044.00CKiUNV573279@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).