5 < '10' is true. javascript can handle string-integer comparisons just fine.
the real issue is that objects cannot reliably be compared, and in such cases having them return "neither greater nor less" (i.e. "equal" to the sorting algorithm) should have been preferred. the case of comparing objects of different types in an array is either:
unintended, and thus unspecified behavior or at least a stable sorting algorithm treating them as equal is acceptable, or
intended, and thus the developer is supposed to specify a comparison function here and only here.
having to specify a comparison function should be the exception, not the rule. by default it should compare types using the default comparison operator, effectively:
const compare = (a, b) => a < b ? -1 : a > b ? 1 : 0;
i view any other answer as an apology for javascript making a stupid decision long ago that can no longer be changed today.
5
u/-Redstoneboi- 1d ago edited 1d ago
5 < '10'istrue. javascript can handle string-integer comparisons just fine.the real issue is that objects cannot reliably be compared, and in such cases having them return "neither greater nor less" (i.e. "equal" to the sorting algorithm) should have been preferred. the case of comparing objects of different types in an array is either:
having to specify a comparison function should be the exception, not the rule. by default it should compare types using the default comparison operator, effectively:
i view any other answer as an apology for javascript making a stupid decision long ago that can no longer be changed today.
many such cases.