🚀 go-pugleaf

>>Speaking of future Apple system software, will Apple ever develop an
>>interface akin to that of the NeXT's or even just X-windows?

>Could you be more specific?  What's missing from the Mac interface
>that's in NeXT or in some X specification (i.e., OpenLook or Motif -- X
>isn't really an interface specification)?

>Are you missing applications?

>Are you missing window management functions?

>If so, what specifically do you want to see?  Apple doesn't supply
>a lot of things because they aren't an applications company.

How about pipes and i/o redirection for starters. There are some activities
that are just better done with a text/command line interface. The power to
set in motion a chain of commands. Multi-directory i/o operations(especially
disjoint directories) are much easier done with a command line. For example,
how would you do this under macOS (send a list of all files under current
directory to the spooled printer)?

  find . -print | lp


Also perhaps what he's refering to is the plethora of programs, scripts, and
utilities that are available on just about any unix machine. Things like awk,
grep, sed, find, etc. that can all be piped together in meaningful ways to
do things that currently are very cumbersome on the mac.
I don't know anything about AUX and I was wondering if somone
could describe how well macOS applications can run under AUX. For example,
if I have AUX running, can I run mac applications in their own windows(or
in an X window)? Can I view and run applications on remote machines as easily
as if they were on my own machine?

Then there is the beautifully seamless networking capabilities of unix 
machines. Unix machines can access many files and run applications on remote
machines from any number of X windows all simultaneously. Can macOS or AUX
do this?  

Inquiring minds want to know?

no sig file here!