From: Brian Peregrine <peregrinebrian@gmail.com>
To: musl@lists.openwall.com
Subject: [musl] Advocating musl to the chromium OS developers
Date: Sat, 14 Mar 2020 17:02:42 +0100 [thread overview]
Message-ID: <CAHCeaGMqEWbBAQk0mjs3dn-CwEO+OEPKUNMOjx07Ekz52FQ=Fg@mail.gmail.com> (raw)
I started a thread at the Chromium OS google groups (called Chromium
OS: compile using musl as default ):
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/iiDRh42EmvE
I think that it would benefit the Chromium OS, but they need to be
convinced more and want more proof (see reply by Kevin). I pointed
them to the musl vs glibc comparison table
(http://www.etalabs.net/compare_libcs.html ) but Mike said:
"the bloat comparison on the musl site is largely irrelevant to us.
it's interesting to embedded people, and to people making comparison
charts, but we could not care less about things like "Smallest static
C program" or "Static hello (using printf)". we don't use static
programs, nor will we ever have any program *not* using a large set of
C library functionality. plus, as Julius points out, the performance
comparison on that site already shows that glibc is generally better
than musl.
The idea why it would be important to get them switched to musl is
because Google is behind Chromium OS and they also develop the
Chromium web browser (and the Chromium browser is in Chromium too I
believe). So, if Chromium OS changes to musl, they'll need to provide
far better support for musl in chromium browser too. Also, having
google developers help out on musl support in the other programs used
by Chromium OS is always a big benefit too.
So, if anyone has any good arguments, go ahead and post them at the
google groups thread (you however do need a google account to post).
next reply other threads:[~2020-03-14 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 16:02 Brian Peregrine [this message]
2020-03-14 17:16 ` Reini Urban
2020-03-14 22:32 ` Rich Felker
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='CAHCeaGMqEWbBAQk0mjs3dn-CwEO+OEPKUNMOjx07Ekz52FQ=Fg@mail.gmail.com' \
--to=peregrinebrian@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).