zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: R Joseph Wright <rjoseph@mammalia.org>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: zsh bloat?
Date: Thu, 20 Jul 2000 22:46:21 +0100 (BST)	[thread overview]
Message-ID: <E13FO97-0005Dq-00@crucigera.fysh.org> (raw)
In-Reply-To: <20000720142630.B6110@manatee.mammalia.org> from R Joseph Wright at "Jul 20, 2000 02:26:30 pm"

R Joseph Wright wrote:
>Zsh shows itself to be smaller than all the others, with the exception of
>ksh, and vastly smaller than bash.  Unless I am missing something, zsh
>seems quite the opposite of bloat.  With all its awesome features, how can 
>it be done?

A lot of zsh's features are not in the main executable, but are now
in separate code modules or shell functions.  Quick check on my laptop
(Red Hat):

$ du -s /opt/zsh/* /bin/ash /bin/bash /bin/tcsh /bin/ksh
342     /opt/zsh/bin
655     /opt/zsh/lib
724     /opt/zsh/man
933     /opt/zsh/share
1858    /opt/zsh/src
63      /bin/ash
313     /bin/bash
253     /bin/tcsh
160     /bin/ksh

So that's 342kB of main binary, 655kB of loadable modules, and 933kB of
shell functions.  (Wow, I didn't realise we had so many functions -- the
current tarballs are now more than twice the size of the 3.1.5 tarball.)
Depending on how you count it, zsh is the largest shell by a factor of
1.1, 3.2 or 6.2.  Of course, in any particular running instance of zsh,
most of those modules and shell functions won't be loaded.  zsh can
also reasonably be installed without any of these extras, making it a
competitively small shell, but with no great interactive features.

-zefram


  parent reply	other threads:[~2000-07-20 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-20 21:26 R Joseph Wright
2000-07-20 21:43 ` Ollivier Robert
2000-07-20 23:51   ` R Joseph Wright
2000-07-20 21:46 ` Zefram [this message]
2000-07-21  7:31 Sven Wischnowsky

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=E13FO97-0005Dq-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=rjoseph@mammalia.org \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).