From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Unix taste (Re: terminal - just for fun)
Date: Sat, 02 Aug 2014 19:04:14 +0300 [thread overview]
Message-ID: <53DD0BFE.3000506@aueb.gr> (raw)
In-Reply-To: <201408021428.s72ESxh5020511@coolidge.cs.dartmouth.edu>
On 02/08/2014 17:28, Doug McIlroy wrote:
> Does comment on taste belong in a discussion of history? I think
> so. Unix was born of a taste for achieving big power by small
> means rather than by unbounded accumulation of facilities. But
> evolution, including the evolution of Unix, does not work that
> way. An interesting question is how the corrective of taste manages
> ever to recenter the exuberance of evolution. The birth of Unix shows
> it can happen. When will it happen again? Can one cite small-scale
> examples that gained traction within the larger evolution of Unix?
With modern facilities (hardware, libraries, distributed open source
development) today's small-scale isn't the same as what it was. If one
considers the exuberant size compared to functionality of Node.js (11M
binary), Emacs (10M), gdb (5.2M), mysql (3.1M), and vim (2.1M), here are
some examples of smaller-scale programs that punch noticeably above
their weight.
- git (1.4M) (as a distributed filesystem with rich metadata and
versioning with configuration management thrown in as a bonus)
- tex (309K)
- curl (154K)
- sudo (121K)
- dot (7.7K plus 730K for its libraries)
- traceroute (53K)
Some libraries that deserve mentioning, when compared to libruby (2.3M),
libxml2 (2.2M), and libpython2.6 (1.6M), are the following:
- libssl (431K)
- liblua (177K)
- C++ STL (816K for /usr/include/c++/4.8.2/bits/stl_*)
* Numbers are "ls -lh" output from a 2014.03 Amazon Linux AMI on which I
had an open shell window.
I also think software package management systems are "small-scale", if
one considers the functionality they offer through the thousands of
packages they can install.
next prev parent reply other threads:[~2014-08-02 16:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2014-08-02 16:03 ` Larry McVoy
2014-08-02 19:36 ` Dave Horsfall
2014-08-02 16:47 Noel Chiappa
2014-08-02 18:51 ` Ian King
2014-08-02 21:18 Noel Chiappa
2014-08-02 23:44 ` A. P. Garcia
2014-08-03 0:48 Noel Chiappa
2014-08-03 8:00 ` A. P. Garcia
2014-08-03 11:49 Noel Chiappa
2014-08-03 12:14 ` Steve Nickolas
2014-08-03 16:26 ` John Cowan
2014-08-04 13:59 ` Tim Bradshaw
2014-08-04 14:53 ` A. P. Garcia
2014-08-03 16:48 Noel Chiappa
2014-08-03 17:09 ` John Cowan
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-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-06 22:19 Norman Wilson
2014-08-06 22:24 Norman Wilson
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=53DD0BFE.3000506@aueb.gr \
--to=dds@aueb.gr \
/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).