The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Unix taste (Re: terminal - just for fun)
Date: Sun, 3 Aug 2014 12:26:34 -0400	[thread overview]
Message-ID: <20140803162634.GB27404@mercury.ccil.org> (raw)
In-Reply-To: <20140803114952.E1AF518C0B4@mercury.lcs.mit.edu>

Noel Chiappa scripsit:

> Exactly. I've often wondered what the heck exactly it is that GNU Emacs, GCC,
> etc are all doing with those megabytes of code. 

GCC is parameterized for a lot more variability than actually exists
nowadays.  As for Emacs, it's traditional to call it bloated because of
all the Elisp code it ships with, but (as esr says in the paper I cited)
that's like calling the shell bloated because there are a lot of shell
scripts out there.  It's a category mistake.

> There's just no reason to have N megabytes of code when .N will
> do. (I've often thought we ought to make new programmers serve an
> apprenticeship of a year of two on a PDP-11 - to teach them to 'think
> small', and to realize you _can_ do a lot in a small space.)

That's basically just the kind of peeving that objects to the use of
computers as calculators and spelling checkers.  "What will Kids Today do
when a calculator isn't available?"  Well, what will they do when there
isn't any ink to dip their goose quills in?  If you're not an angel,
there is no real advantage to learning to dance on the head of a pin.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
        You tollerday donsk?  N.  You tolkatiff scowegian?  Nn.
        You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
                Clear all so!  `Tis a Jute.... (Finnegans Wake 16.5)



  parent reply	other threads:[~2014-08-03 16:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 11:49 Noel Chiappa
2014-08-03 12:14 ` Steve Nickolas
2014-08-03 16:26 ` John Cowan [this message]
2014-08-04 13:59 ` Tim Bradshaw
2014-08-04 14:53   ` A. P. Garcia
  -- strict thread matches above, loose matches on Subject: below --
2014-08-06 22:24 Norman Wilson
2014-08-06 22:19 Norman Wilson
2014-08-04 20:21 Norman Wilson
2014-08-04 22:24 ` A. P. Garcia
2014-08-05  2:41   ` Andy Kosela
2014-08-05  3:32     ` Warner Losh
2014-08-04  2:54 Norman Wilson
2014-08-04  3:11 ` Lyndon Nerenberg
2014-08-04  7:04   ` Dave Horsfall
2014-08-04  9:12     ` Steve Nickolas
2014-08-03 16:48 Noel Chiappa
2014-08-03 17:09 ` John Cowan
2014-08-03  0:48 Noel Chiappa
2014-08-03  8:00 ` A. P. Garcia
2014-08-02 21:18 Noel Chiappa
2014-08-02 23:44 ` A. P. Garcia
2014-08-02 16:47 Noel Chiappa
2014-08-02 18:51 ` Ian King
2014-08-02 14:28 Doug McIlroy
2014-08-02 14:00 ` Larry McVoy
2014-08-02 15:51   ` Steve Nickolas
2014-08-02 16:07     ` John Cowan
2014-08-02 17:28     ` Benjamin Huntsman
2014-08-02 19:50     ` Dave Horsfall
2014-08-02 16:04 ` Diomidis Spinellis
2014-08-02 16:03   ` Larry McVoy
2014-08-02 19:36 ` Dave Horsfall

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=20140803162634.GB27404@mercury.ccil.org \
    --to=cowan@mercury.ccil.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).