From: clemc@ccc.com (Clem Cole)
Subject: [TUHS} Running V8 ...
Date: Mon, 16 Oct 2017 12:28:23 -0400 [thread overview]
Message-ID: <CAC20D2PBkRgoyrmQ+wDpqfZ7kXCUqNWdJgm08EO2djmwFp4Fng@mail.gmail.com> (raw)
In-Reply-To: <201710161158.v9GBweD4005539@coolidge.cs.Dartmouth.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
On Mon, Oct 16, 2017 at 7:58 AM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>
> This question bears on a recent thread about favorite flavors of Unix. My
> favorite flavor is Universal Unix, namely the stuff that just works
> everywhere. That's essentially what K&P is about.
+1 I would add, to me that's what the 'standardization' efforts were
really about as a >>user<<. To settle on the minimum subset needed to the
get the job do and stop adding 'sugar' because you could. The ISVs wanted
to maximize (SPEC1170 et al), but to me 'Universal' was what do I really
need/use every day.
In fact, its why I switch from EMACS to vi early in my UNIX career. Vi
and (ed) were everywhere (K&P style). EMACS was not and if I found a
flavor for that system, it was always 'different.' I could sit down at
anything from MS-DOS to a Cray and stuff worked well enough that I could do
what I needed to do. [I'm not a great fan of "vim" for that reason either
BTW -- I just want the basics to 'be there' and 'be reliable' - do what I
want without me having to rethink].
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171016/b64274eb/attachment-0001.html>
next prev parent reply other threads:[~2017-10-16 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 11:58 Doug McIlroy
2017-10-16 15:41 ` Don Hopkins
2017-10-17 11:47 ` Tony Finch
2017-10-17 14:30 ` Larry McVoy
2017-10-17 14:50 ` Don Hopkins
2017-10-16 16:28 ` Clem Cole [this message]
2017-10-16 16:39 ` [TUHS} Running V8 ... [ really basic tools ] Jon Steinhart
2017-10-16 19:16 ` Ian Zimmerman
2017-10-16 19:28 ` Jon Steinhart
2017-10-17 1:15 ` Ian Zimmerman
2017-10-17 4:20 ` UNIX version 2*pi Don Hopkins
2017-10-17 6:08 ` Dave Horsfall
2017-10-17 18:23 ` Ron Natalie
2017-10-18 2:46 ` Dave Horsfall
2017-10-18 10:15 ` Ron Natalie
2017-10-16 16:38 ` [TUHS} Running V8 Will Senn
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=CAC20D2PBkRgoyrmQ+wDpqfZ7kXCUqNWdJgm08EO2djmwFp4Fng@mail.gmail.com \
--to=clemc@ccc.com \
/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).