mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jacob Welsh <jacob+musl@welshcomputing.com>
To: musl@lists.openwall.com
Subject: [musl] Locale support considered harmful noise
Date: Tue, 18 Feb 2020 19:38:29 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.2002181937050.23857@ny4.eemta.org> (raw)

Hello,

In TMSR we've made extensive use of musl, due to the very welcome dose of clear and concise code it provides as compared to the competition [1]. For example we have a static Ada compiler [2], the Bitcoin reference implementation [3], a reproducible and self-contained Gentoo system [4], and not least of all my own distribution [5] used in my consulting business [6].

However, the apparent goal of aggressive expansion of Unicode and localization "features" in musl sets off alarms; for instance, on the roadmap [7] I see:

> Unicode 12.1 update and related character handling work

> Locale support overhaul.

> Hostname resolver support for non-ASCII domains (IDN)

> LC_COLLATE support for collation orders other than simple codepoint order

> Support for LC_MONETARY and LC_NUMERIC properties.

> Message translation support for dynamic linker

> Locale data and libc message translations

We think this is such a bad idea that it threatens to undermine musl's otherwise substantial virtues. This kind of bloat imposes real costs on the users that matter - namely the literate ones, who value predictable, stable and bug-free code - in exchange for entirely unclear benefits.

Especially considering the rate at which bugs are still turning up, there is no justification for this added complexity. In any event we will not be using "upgrades" that import additional nonsense into this critical system component.

I'll be happy to discuss further here, in my blog comments or on irc [8].

Yours,
J. Welsh

[1] http://trinque.org/2019/12/29/a-republican-os-part-2/
[2] http://ave1.org/2018/building-gnat-on-musl/
[3] http://therealbitcoin.org/ml/btc-dev/2015-July/000133.html
[4] http://trinque.org/2018/11/27/cuntoo-bootstrapper/
[5] http://fixpoint.welshcomputing.com/2019/introducing-gales-linux
[6] http://dorion-mode.com/2019/11/jwrd-computing
[7] https://wiki.musl-libc.org/roadmap.html
[8] #ossasepia or #trilema on freenode; PM me (jfw) or someone talking to ask for voice.

             reply	other threads:[~2020-02-18 19:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 19:38 Jacob Welsh [this message]
2020-02-18 21:42 ` A. Wilcox
2020-02-18 22:23   ` Hadrien Lacour
2020-02-18 23:29     ` [musl] race condition in sem_wait Sebastian Gottschall
2020-02-19  0:46       ` Sebastian Gottschall
2020-02-19  3:39         ` Rich Felker
2020-02-19  8:26           ` Sebastian Gottschall
2020-02-19 14:13             ` Rich Felker
2020-02-19  4:07         ` Bobby Bingham
2020-02-19 21:28   ` [musl] Locale support considered harmful noise Jacob Welsh
2020-02-19 22:06     ` Rich Felker
2020-02-19  3:36 ` 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=alpine.DEB.2.00.2002181937050.23857@ny4.eemta.org \
    --to=jacob+musl@welshcomputing.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).