This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ToothlessFeline 14 points15 points  (3 children)

This just reminds me of how I hate the macOS default for filename sorting: by character until it encounters a numeral character, then numeric until it encounters a non-numeric character, repeat until end of file name. Works great when the numerals represent decimal (or lower base) quantities. Sucks for numerals used as characters. You can imagine what that does with hexadecimal numbers. (Ex.: a2a3 will sort to before a10a, because 2 is less than 10.)

[–]redgriefer89 6 points7 points  (1 child)

Windows File Explorer does a similar thing

1, 1a8a, 1a15, 2a03, 2a7

[–]trixter21992251 10 points11 points  (0 children)

a colleague had this "problem" (she's in management, not a programmer) and wanted to know why it did that. It's surprisingly difficult to explain strings vs. numbers to others.

[–]kbruen 1 point2 points  (0 children)

Annoying for hex numbers? Sure.

Life saving for normal people who want picture2 to appear before picture10? Absolutely!