News for hackers. Stuff that matters.
Re:Unicode is harder than you think by tialaramex on Tuesday July 25, 2023 @07:28PM (#36871144)
People expect Strings. You don't have to provide strings, but you should be aware that people expect them and if you provide something else but don't clearly label it as not strings there's an excellent chance they'll go "Oh, strings" and then they'll complain that it doesn't work the way they expected.

If I can write "foo".contains('o') or similar in your language, but then you pretend you don't have strings, nobody will believe you and they're quite right to complain when, inevitably, lots of trickier stuff doesn't work because you didn't bother.

WUFFS doesn't have strings. But WUFFS isn't a general purpose language. Fortran has strings. C has strings (they're terrible but they're clearly strings).

Re:Unicode is harder than you think by alcover on Tuesday July 25, 2023 @07:53PM (#36871334)
> If I can write "foo".contains('o') [..] but then you pretend you don't have strings, [..] C has strings

By your logic, couldn't I pretend then to have strings insomuch as C when "foo".contains('o') can be transpiled by my lang as

  strchr("foo", 'o') != NULL
Re:Unicode is harder than you think by tialaramex on Tuesday July 25, 2023 @11:39PM (#36872805)
You could definitely have C's terrible strings, yes. But it is 2023 so that seems like aiming very low indeed