The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Unix taste (Re: terminal - just for fun)
Date: Sun, 3 Aug 2014 12:14:49 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.02.1408031211520.7442@localhost> (raw)
In-Reply-To: <20140803114952.E1AF518C0B4@mercury.lcs.mit.edu>

On Sun, 3 Aug 2014, Noel Chiappa wrote:

>    > From: "A. P. Garcia" <a.phillip.garcia at gmail.com>
>
>    > the spirit of emacs without the bloat :-)
>
> Exactly. I've often wondered what the heck exactly it is that GNU Emacs, GCC,
> etc are all doing with those megabytes of code. (In part, probably all those
> options: "Options. We've got lots of them. So many in fact, that you need two
> strong people to carry the documentation around.", as that classic hack says.
> But there's no way the options alone can explain it all.)

GNU is, and always has been, a waste of space.  I use it, but I think 
BSD's lean and mean approach is superior.

> The thing is that it's not just aesthetics that makes large programs bad;
> there are very good practical reasons why they are bad, too. The 'takes more
> resources' isn't such a big deal today, because memory is massive, and
> there's a ton of computing power to be thrown at things. (Although I'm always
> amazed at how the active content in Web pages seems to run incredibly slowly
> on all but the very latest and greatest machines. WTF are they doing?)

EVERYTHING runs incredibly slow.  Gates' law - the apparent speed of 
software halves every 18 months. :P

> But more code = more material that someone new has to understand before they
> can make some change (and long-lived code is always being changed/upgraded by
> new people). And when people understand a system poorly, their changes tend
> to be 'a bag on the side', and that's the kind of 'code cancer' that tends to
> kill systems in the long run. More code also is also more places where there
> can be bugs (especially when it's changed by someone who understands it
> poorly, repeat previous comment).
>
> Etc, etc. And those will never go away - human brain power is finite, and
> unlike hardware, not expanding.
>
> 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.)

QFT.

I actually do a lot of programming in an even tighter space: 64K Apple //e 
target.  Horrible machine for C, but it's a relatively simple machine to 
grok except for the disk controller =P

-uso.



  reply	other threads:[~2014-08-03 12:14 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 [this message]
2014-08-03 16:26 ` John Cowan
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=alpine.DEB.2.02.1408031211520.7442@localhost \
    --to=usotsuki@buric.co \
    /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).