Earlier quoted context omitted.
> It's not a big advantage. EBCDIC, for example, didn't do that, and programmers managed just fine without it. You might try asking an old IBM programmer just how "fine" they felt dealing with EBCDIC...
EBCDIC had many problems, agreed. One is the non-contiguous range. Another is the many variants ( https://en.wikipedia.org/wiki/EBCDIC_code_pages lists 11, x2 for the Euro Update). But how serious is the problem? How many times do you need to test if a given character is one of the 26 allowed letters of the English alphabet, and where you implement it by testing it against the range? Typically you write it as "islowe…
We've broadly moved beyond that, but there's still value in grouping sets together in a way that makes certain kinds of frequent tests less computationally expensive than they would be if codepoints were randomly distributed.