(High roller, I know.)
No games, though. If you say "An algorithm to compute the length of the string in number of visible characters," that obviously is designed to pass the test rather than to do anything useful.
Maybe framing it as a bet will break the illusion that string length is ever required.
I guess what I amsaying is:where are you marking the diffefence? any string (and all data) IS at the a series of encoded bites
> I'll paypal $20 to anyone who can name a situation where string length (in number of visible characters) is actually required by any reasonable algorithm.
And this is completely reasonable. He is a human, not "a computer person" (his terminology) and pays me to abstract from him those "computer things" which he has no desire to understand.
Then he might have to learn it's very much a "human", not "computer" thing...
My original response was going to be that you don't actually care about "foo".length in that context, either. You care whether one string is larger than the other, i.e. the actual value doesn't matter -- all that matters is that if a string X is longer than string Y, then the length should increase. But mathematically, that's just a precise definition of requiring the string length, so that logic doesn't work out.
If you email me your paypal/venmo/whatever, you can collect the $20, since you were the first to point out monospaced font. I still feel that monospaced fonts are sidestepping the whole point, but I won't be pedantic about it.
(https://news.ycombinator.com/item?id=29303325 points out why this isn't a sensible operation, if you were curious about why I feel inclined not to concede the bet.)
Just for more context, I was thinking data tables: like this.
There are lots to choose from, and I suppose I don't really care about making a perfect choice. I'm mostly just curious what other people donate to.
Re: the data tables, it's tempting to think that you need the string length for that case. But what you really care about is whether the strings start at the same place, and whether the string fits in a column -- both of which are questions best answered by a font subsystem rather than relying on string length.
But the data table case is so common that I agree it fulfills the terms of the bet, in the strictest sense. But e.g. that Competition / Name column will break for various non-English languages if you try to base the formatting on "number of visible characters."
I think you'd find most people donate based on what's touched their lives, e.g. breast cancer research if you lost a loved on to breast cancer.
If you believe climate change is the existential crisis, then that's a good avenue to explore. e.g., https://www.rainforestcoalition.org/
I ended up donating $200 to this kid who lost his finger and then got a staph infection: https://watsi.org/profile/08a347b3594d-savy
And then fulfilled the bet by donating $20 to Watsi.
E.g., most Asian characters & emoji are 2 cell widths in a fixed with font for a single character. The character "e" is 1 byte in UTF-8, "é" is >1. The "family of four" emoji can be up to 11 code points, 41 bytes (in utf-8), and 2 cell widths (still just an emoji) and is, I presume, a single grapheme cluster.
Which is 99% of the work to also calculate the length in those terms.
I'm still struggling with this in one place, where, for some reason, Cyrillic characters get cut in half.
You may visualize all that by converting your strings to lists of bytes.
If uppercase requires a diacritic, but lower case didn't that doesn't (usually) increase the visible character count, but it likely increases storage space, depending on encodings and normalization forms. Thinking about i to I with dot (which I can't currently type), which would need more storage in utf-8 or as I + dot.
I suppose some terminal rendering (where you're taking in chunks and you might want to be a bit clever about jumping to spaces to figure out where breaks should go).
There is a notion of UTF codepoints that you can index into (see how Python does string indexing), though I generally think that people who whine a lot about string behavior for UTF tend to just not be reaching for the right tools.
"What size does this UI element have to fit this text in our specific mono-spaced font"?
“Full name” and “username” must both have a minimum length of 1.
That's what Twitter's tweet limit ought to be, and if there was an easy, culturally neutral algorithm for it I'm sure that's what they would have done.