Maybe this should be part of a general-purpose pluggable sorting API

[sffc]

I think @bakkot brought up today that JS might want to work in the direction of having more comparators for various use cases.

This proposal would fit very well into such a framework, better than as a free function on String. Can we investigate that direction?

[bakkot]

I do want to ensure that we are considering how this can evolve towards a world where JS provides more comparators; e.g. I would want this to establish precedent for how we provide comparators in general.

But I think even in such a world this might still make sense to have this available as a static function on String. For example, we might say the convention is that sortable types have a compare or compareViaSomeStrategy static function, along the lines of Number.compare and so on; this convention would be better than having a Compare.number and Compare.stringByCodePoints because it is a convention user types can follow as well. (I note that Temporal already follows this convention.)

See also #6 which discusses a way we could provide the building blocks of this function rather than providing this function itself (though as some people have said in that issue even with those blocks available we could still provide this function as well).