Void Linux discussion
 help / color / mirror / Atom feed
From: Christian Neukirchen <chneuk...@gmail.com>
To: "Stefan Mühlinghaus" <"master..."@googlemail.com>
Cc: void...@googlegroups.com
Subject: Re: glibc vs musl - what is the difference for daily usage ?
Date: Wed, 17 Jun 2015 11:58:48 +0200	[thread overview]
Message-ID: <87a8vy8xlz.fsf@gmail.com> (raw)
In-Reply-To: <c70d1273-79c1-41ae-9956-1f79b15e911c@googlegroups.com> ("Stefan \=\?utf-8\?Q\?M\=C3\=BChlinghaus\=22's\?\= message of "Tue, 16 Jun 2015 10:39:06 -0700 (PDT)")

Stefan Mühlinghaus <master...@googlemail.com> writes:

> I would be interested in that as well. Is there any *tangible* benefit in 
> using the musl libc except having the warm fuzzies from using the leaner 
> technology? :)
> I hesitate to switch to musl for fear of running into incompatibilities, 
> but that could just be my superstitious self.

Just a few additions:

- MIT license, so you could build a GPL-free userland with it.
- Good support for static linking.
- Huge focus on correctness (which means in practice that sloppily
  written software can break...).
- Good UTF-8 support.
- Support for new and experimental architectures.

Also see http://www.etalabs.net/compare_libcs.html

-- 
Christian Neukirchen  <chneuk...@gmail.com>  http://chneukirchen.org

  parent reply	other threads:[~2015-06-17  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 17:08 Frankie Wild
2015-06-16 17:39 ` Stefan Mühlinghaus
2015-06-16 22:17   ` Chris Brannon
2015-06-17  9:58   ` Christian Neukirchen [this message]
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=87a8vy8xlz.fsf@gmail.com \
    --to="chneuk..."@gmail.com \
    --cc="master..."@googlemail.com \
    --cc="void..."@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).