From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Charles Forsyth on putting Unix on a diet.
Date: Fri, 27 Oct 2017 16:04:10 -0700 [thread overview]
Message-ID: <20171027230410.GG6118@mcvoy.com> (raw)
In-Reply-To: <CALMnNGiKFq4UpdOxqoit1+24vakP=qH6bn+PsQxtApSQOVKOXg@mail.gmail.com>
On Fri, Oct 27, 2017 at 11:51:12PM +0200, Andy Kosela wrote:
> It seems that it is very hard to avoid bloat in the software world in the
> long run. Most people don't care, but the original UNIX and C, Plan 9 and
> Go projects could be one of the few I can think of that really cared about
> minimalism.
We cared. We being the BitKeeper guys.
BK as of 2002 (bk-2.0.5):
33 documented commands
wc *.c
67633 225563 1565556 total
BK as of 15 years later (bk-7.3.2)
165 documented commands
wc *.c
125812 444197 3017977 total
So we doubled in size for all the built in commands but we had 5x as many
commands. A huge amount of functionality over the bk-2.x era.
The only way we did that was by encouraging and rewarding commits that took
out as much as they put in.
It's possible but you have to be disciplined.
--lm
next prev parent reply other threads:[~2017-10-27 23:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 10:36 Noel Chiappa
2017-10-27 13:03 ` Clem Cole
2017-10-27 13:23 ` Steve Nickolas
2017-10-27 21:51 ` Andy Kosela
2017-10-27 23:04 ` Larry McVoy [this message]
2017-10-27 23:15 ` Steve Simon
2017-10-27 23:39 ` Tim Bradshaw
2017-10-28 2:00 ` Bakul Shah
2017-10-28 2:34 ` Lyndon Nerenberg
2017-10-28 2:42 ` Lyndon Nerenberg
2017-10-28 6:38 ` Bakul Shah
2017-10-27 21:43 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-10-28 13:11 Norman Wilson
2017-10-27 21:30 Norman Wilson
2017-10-27 22:49 ` Chris Torek
2017-10-26 14:57 Doug McIlroy
2017-10-26 22:07 ` George Michaelson
2017-10-25 2:51 Dan Cross
2017-10-25 3:14 ` Larry McVoy
2017-10-26 17:27 ` Larry McVoy
2017-10-26 22:12 ` George Michaelson
2017-10-27 3:49 ` Steve Nickolas
2017-10-27 6:55 ` arnold
2017-10-27 7:30 ` Derek Fawcus
2017-10-27 9:44 ` David Arnold
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=20171027230410.GG6118@mcvoy.com \
--to=lm@mcvoy.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).