From: Andrew Warkentin <andreww591@gmail.com>
To: coff@tuhs.org
Subject: Re: [COFF] Powershell better than Bourne shell?
Date: Thu, 18 Nov 2021 23:19:25 -0700 [thread overview]
Message-ID: <CAD-qYGovNTQH-jF4A5bGkCiN55u1e7=8oEhwN=GatqTO+=AVeQ@mail.gmail.com> (raw)
In-Reply-To: <CAP2nic2V7uFz0nR_sB1f0jAUegnUJcnm-E_9FVomYeK1E59BrQ@mail.gmail.com>
(mistakenly sent this as a private message and not to the list)
On 11/18/21, Adam Thornton <athornton@gmail.com> wrote:
> It’s not an insane claim.
>
> PS is way wordier but it does deal with structured objects rather than just
> byte streams.
>
> I think of PS as being a closer match to VM/CMS Pipelines (but much less
> elegant).
>
> There are arguments to be made both ways. I generally prefer the byte
> stream where the producer and consumer have to agree on the format, but,
> well, Unix is my homeland.
>
> I guess I argue that PS minus IPC is COBOL to Bourne Shell’s C. Some
> people prefer it and de gustibus non est disputandum.
>
The biggest issue I have with PowerShell besides its verbosity is that
commands have to be implemented as plugins rather than as external
programs.
I'm thinking at some point I may write a Bourne-like shell with
object-oriented features for the OS that I'm working on. Instead of
requiring commands to be plugins to use the object-oriented features I
am thinking of having a generic facility for serialization and
deserialization with hooks to deal with the output format of different
commands (with JSON being an option as well).
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-11-19 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 23:03 Greg 'groggy' Lehey
2021-11-19 1:12 ` Grant Taylor via COFF
2021-11-19 23:00 ` Theodore Y. Ts'o
2021-11-20 15:54 ` Michael Kjörling
2021-11-19 5:15 ` Adam Thornton
2021-11-19 6:19 ` Andrew Warkentin [this message]
2021-11-19 18:44 ` Steffen Nurpmeso
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='CAD-qYGovNTQH-jF4A5bGkCiN55u1e7=8oEhwN=GatqTO+=AVeQ@mail.gmail.com' \
--to=andreww591@gmail.com \
--cc=coff@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).