From: "Iruata Souza" <iru.muzgo@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Announce: standalone libixp
Date: Sun, 1 Jul 2007 13:15:11 -0300 [thread overview]
Message-ID: <d1c554290707010915y5c20ba74o6852fdad7f0d777@mail.gmail.com> (raw)
In-Reply-To: <20070701125003.GB10308@nibiru.local>
On 7/1/07, Enrico Weigelt <weigelt@metux.de> wrote:
> * Kris Maglione <bsdaemon@comcast.net> wrote:
> > On Sat, Jun 30, 2007 at 07:30:41PM +0200, Enrico Weigelt wrote:
> > >Don't you want people the freedom to choose what they like best ?
> >
> > There is no choice involved. If you install a shared library,
> > it will be used by default on most systems.
>
> This realy depends on how the application is built.
>
> > >There are valid reasons for using shared libraries, ie. not the
> > >need to rebuild applications on library update or saving resources.
> >
> > Saving resources is not relevant here.
>
> For me it really *IS* relevant. I'm working in embedded environments
> with very limited resources.
>
> > libixp is so small that the resources required to dynamically link
> > it are greater than those required to statically link it.
>
> Well, if it would be just a few pages, you maybe could be true.
> But (at least at my site) the .a is about 100k and the the .so
> about 90k large.
>
not to troll on you, enrico,
but this thread remembered me of one on the openbsd-tech list.
the situation was: someone proposed a -l option to openbsds ifconfig
just to list network interface names. ifconfig already shows the names
and much more info so the -l behaviour can obsviously be achieved with
shell scripting. at some point in the discussion someone said about -l
being a good point for embedded since it lets you cut off sed, awk and
that sort of utility with the same space argument.
this is what i answered http://marc.info/?l=openbsd-tech&m=115103143012683&w=2
iru
next prev parent reply other threads:[~2007-07-01 16:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 15:38 Enrico Weigelt
2007-06-30 16:47 ` Kris Maglione
2007-06-30 16:50 ` Kris Maglione
2007-06-30 17:30 ` Enrico Weigelt
2007-06-30 17:41 ` Kris Maglione
2007-07-01 12:50 ` Enrico Weigelt
2007-07-01 16:15 ` Iruata Souza [this message]
2007-07-01 10:11 ` Charles Forsyth
[not found] ` <dba1bd02516b1cfbf4119d7c567ec8e9@terzarima.net>
2007-07-01 12:42 ` Enrico Weigelt
2007-06-30 16:47 ` Uriel
2007-07-01 23:22 ` Roman Shaposhnik
2007-07-02 0:45 ` Enrico Weigelt
2007-07-03 3:50 ` Roman Shaposhnik
2007-07-03 4:09 ` Kris Maglione
2007-07-03 15:10 ` Enrico Weigelt
2007-07-03 19:45 ` Federico Benavento
2007-07-03 20:31 ` Jonathan Cast
2007-07-03 21:14 ` Wes Kussmaul
2007-07-03 21:51 ` Martin Neubauer
2007-07-03 23:16 ` Enrico Weigelt
2007-07-04 3:36 ` Iruata Souza
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=d1c554290707010915y5c20ba74o6852fdad7f0d777@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).