mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <>
To: enh <>
Subject: Re: [musl] A journey of weird file sorting and desktop systems
Date: Fri, 28 Jan 2022 14:22:48 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jan 28, 2022 at 10:33:53AM -0800, enh wrote:
> On Fri, Jan 28, 2022 at 10:01 AM Rich Felker <> wrote:
> >
> > On Fri, Jan 28, 2022 at 08:58:30AM -0800, enh wrote:
> > > (Android's libc maintainer here...)
> > >
> > > i'd argue this isn't a musl bug. on Android we make a clear distinction between:
> > >
> > > 1. libc's responsibilities which, to paraphrase rich, are basically
> > > "be unsurprising because your audience is OS/app developers who don't
> > > speak all the languages their users use anyway". that is: "code point
> > > order".
> >
> > That's not what I said. I speculated that part of the difficulty with
> > getting people to care is that a large number of users personally
> > prefer LC_COLLATE=C. Not that we should punt because of that.
> >
> > > 2. icu's responsibilities which cover all the user-facing (as opposed
> > > to developer-facing) stuff. i18n is *hard* and the C/POSIX APIs are,
> > > to be blunt, not fit for *that* purpose. there's a reason why all of
> > > Android/macOS/Windows (and all the browsers) ship copies of icu.
> >
> > ICU is really, *really* bad. I don't want to be encouraging people to
> > use it because basic functionality is missing from libc.
> human languages are really really messy. a lot of the complexity is inherent.
> as for the non-inherent, seems
> like a good start.

The problems with ICU are all software engineering problems not
problem-domain complexity problems. Bad resource-hungry choices with
poor safety properties all over.

> > > the bug here is that a desktop file manager is assuming "i just want
> > > telephone book order --- how hard can it be?". the answer turns out to
> > > be "hard". especially when you get into fun stuff like users who *do*
> > > speak multiple languages and have strong expectations for how they
> > > sort. or places where there are multiple sort orders in common use.
> >
> > Absolutely. That's why I don't want to treat the problem half-assedly,
> but that's my point --- it's not the *implementation* that's the
> issue, it's that the C/POSIX *interfaces* are insufficient. the bar on
> how good a job you _can_ do within those constraints is horribly low.

I'm not sure what you mean by "the interfaces are insufficient" here.
They're insufficient to do things they weren't meant to do (e.g. deal
with data with multiple cultural conventions where the data has to be
tagged with which conventions apply to it), but giving listings in a
user's chosen collation order convention is something they're
perfectly capable of doing. Most applications do not want to deal with
(and do not even have the necessary metadata to deal with, since the
raw data is plain text) the sort of mix the standard interfaces can't
handle. They just want to give decent, culturally-non-surprising UX.
Applications that do want to go beyond this can of course use the full
Unicode data (via ICU or ideally a better alternative).


  reply	other threads:[~2022-01-28 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 13:41 ellie
2022-01-28 14:10 ` Rich Felker
2022-01-28 14:57   ` ellie
2022-01-28 16:58     ` enh
2022-01-28 18:01       ` Rich Felker
2022-01-28 18:33         ` enh
2022-01-28 19:22           ` Rich Felker [this message]
2022-01-28 19:47         ` Markus Wichmann
2022-01-28 18:01     ` Ariadne Conill
2022-01-28 17:54   ` Ariadne Conill

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).