From: Frankie Wild <green...@gmail.com>
To: voidlinux@googlegroups.com
Subject: glibc vs musl - what is the difference for daily usage ?
Date: Mon, 15 Jun 2015 10:08:14 -0700 (PDT) [thread overview]
Message-ID: <1cfda652-6fa2-4d44-ab36-3f17f3be26ef@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]
There is quite a lot of steer around musl those days. I have tried musl
compiled mate based image of Void on virtual machine, but since Void is so
fast I couldn't notice any difference between glibc images I have tried in
the past.
I have read stuff about smaller size, faster performance, but in reality it
looks negligible. Is there more to it in the long run ? And what are the
cons ?
[-- Attachment #1.2: Type: text/html, Size: 439 bytes --]
next reply other threads:[~2015-06-15 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 17:08 Frankie Wild [this message]
2015-06-16 17:39 ` Stefan Mühlinghaus
2015-06-16 22:17 ` Chris Brannon
2015-06-17 9:58 ` Christian Neukirchen
2015-06-24 7:04 ` Frankie Wild
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=1cfda652-6fa2-4d44-ab36-3f17f3be26ef@googlegroups.com \
--to="green..."@gmail.com \
--cc=voidlinux@googlegroups.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).