Sum up of the discussions on the repo:

Emmanuel favors adding the native option. Sanne is against.

withComparator is likely too hard to do and not portable so will be removed for first round.

Pending discussion on in(Unit), should we keep it?

Sanne wants to remove andByScore as he sees the use case useless. Emmanuel has seen it in various (ES) example, should we eliminate it?

Sanne wants to remove andByIndexOrder as he sees it only used for a single "non-sort" option.

Sanne does not want withComputeMethod, Emmanuel would like it but could be done as a second step. OTOH, we know what happens to second steps, they are never done.

Exclude MultiValuedMode for now and HSEARCH does not support sort on multivalue but we should open an issue to support it.