The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "A. P. Garcia" <a.phillip.garcia@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: TUHS <tuhs@tuhs.org>, Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Subject: [TUHS] Re: most direct Unix descendant
Date: Sun, 9 Jun 2024 10:06:00 -0400	[thread overview]
Message-ID: <CAFCBnZshf660L8N8srBTpYxuAzc+wZvxgzNpSgdfY2ar+Z-nqQ@mail.gmail.com> (raw)
In-Reply-To: <20240609123155.7C72220152@orac.inputplus.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

On Sun, Jun 9, 2024, 8:40 AM Ralph Corderoy <ralph@inputplus.co.uk> wrote:

> Hi A. P.,
>
> > All major apps have Powershell libraries.  I envy some features of
> > Powershell, but I still won't use it unless I have to.
> >
> > One example is PowerCLI, which is very useful for vSphere automation.
> > Easier to use than their other language APIs, in my opinion.
>
> The grandfather of your post address Powershell earlier on.
>
>
> https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/message/QZVFRCYM2MEJ4VNZPORBUAKIS6WG6LIY/
> > The concept of producing a stream of text as the output of a program
> > that does simple jobs well has been replaced by "power-shell" thinking
> > of passing binary objects rather than text between program
> > - a decidedly non-portable idea.
> >
> > Passing "objects" requires attaching to a dynamically linked library
> > (that will change or even disappear with the next release of the OS or
> > the object library).  With Research Unix, I could pipe the output of
> > a Unix program running on an Intel 486 to another program running on
> > a Motorola 68000 or a Zilog Z80000 or an IBM AIX machine.
>
> --
> Cheers, Ralph.
>

Thank you, I hadn't seen that. He's right, of course. It's kludgy, but you
can always use text, or some structured form of it like json or xml, to
communicate between different machines. Does windows have something like
netcat/socat? I honestly don't know.

>

[-- Attachment #2: Type: text/html, Size: 2243 bytes --]

  reply	other threads:[~2024-06-09 14:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 11:34 Douglas McIlroy
2024-06-09 11:59 ` A. P. Garcia
2024-06-09 12:31   ` Ralph Corderoy
2024-06-09 14:06     ` A. P. Garcia [this message]
2024-06-10  5:13   ` Ed Bradford
2024-06-10  5:25     ` G. Branden Robinson
2024-06-10  8:39     ` Dave Horsfall
2024-06-10  9:36       ` Marc Donner
2024-06-10 19:40         ` Steffen Nurpmeso
2024-06-10 20:09           ` Marc Donner
2024-06-10 20:19             ` Steffen Nurpmeso
2024-06-11  3:15       ` [TUHS] Re: Likely a one-liner in Unix James Frew
2024-06-11  8:05         ` Ralph Corderoy
2024-06-11 21:01           ` Steffen Nurpmeso
     [not found] <1324869037.1755756.1717582639424.ref@mail.yahoo.com>
2024-06-05 10:17 ` [TUHS] most direct Unix descendant Andrew Lynch via TUHS
2024-06-05 10:51   ` [TUHS] " Andrew Warkentin
2024-06-05 13:46     ` Andrew Lynch via TUHS
2024-06-05 17:34   ` segaloco via TUHS
2024-06-05 17:51     ` Will Senn
2024-06-05 18:02       ` ron minnich
2024-06-05 23:07         ` Andrew Warkentin
2024-06-05 18:22       ` Jeffrey Joshua Rollin
2024-06-05 18:41         ` Warner Losh
2024-06-05 19:17           ` Jeffrey Joshua Rollin
2024-06-06  9:55             ` Ralph Corderoy
2024-06-06 19:49               ` Steffen Nurpmeso
2024-06-09  8:00                 ` Ed Bradford

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=CAFCBnZshf660L8N8srBTpYxuAzc+wZvxgzNpSgdfY2ar+Z-nqQ@mail.gmail.com \
    --to=a.phillip.garcia@gmail.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=ralph@inputplus.co.uk \
    --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).