Re: Command Languages Versus Programming Languages

El Wed, 2 Oct 2024 07:10:32 -0000 (UTC), Muttley escribió:

On Tue, 1 Oct 2024 20:18:28 -0000 (UTC)
usuario <anthk@disroot.org> boring babbled:

El Mon, 30 Sep 2024 21:04:24 -0000 (UTC), Lawrence D'Oliveiro escribió:
>

On Mon, 30 Sep 2024 20:04:54 -0000 (UTC), Bozo User wrote:
 

Perl is more awk+sed+sh in a single language. Basically the killer of
the Unix philophy in late 90's/early 00's, and for the good.

 
That’s what Rob Pike said
<https://interviews.slashdot.org/story/04/10/18/1153211/rob-pike-

responds>:

 
    Q: “Given the nature of current operating systems and
    applications,
    do you think the idea of "one tool doing one job well" has been
    abandoned?”
    A: “Those days are dead and gone and the eulogy was delivered by
    Perl.”
 
But I’m not sure I agree. Those small, specialized tools always
required large, monolithic pieces under them to operate: the shell
itself for shell scripts, the X server for GUI apps, the kernel itself
for everything. So while the coming of Perl has changed some things,
it has not made a difference to the modularity of the Unix way.

>
The shell could be changed as just a command launcher with no
conditionals, while perl doing all the hard work.
>
On X11/X.org, X11 was never very "Unix like" by itself.

 
An X server is about as minimal as you can have a graphics system and
still make it usable. I don't see how it could have been subdivided any
further and still work.

Check out Blit under Unix V10 and Rio under plan9/9front for a much better
Unix-oriented (9front/plan9 it's basically Unix philosophy 2.0) approach.