zlacker

[parent] [thread] 3 comments
1. vidarh+(OP)[view] [source] 2026-01-20 17:14:08
Well, we can see the string, and we can see that is uses plain ASCII.
replies(1): >>e12e+j3
2. e12e+j3[view] [source] 2026-01-20 17:24:42
>>vidarh+(OP)
In this case, sure. But what if we shifted to rendering with emojis or whatnot. What would the first ASCII character of the string be?
replies(1): >>vidarh+L33
◧◩
3. vidarh+L33[view] [source] [discussion] 2026-01-21 14:40:03
>>e12e+j3
If you anticipate that need, you just store the gradient as an array of strings, and you still then only need a trivial lookup.
replies(1): >>e12e+o45
◧◩◪
4. e12e+o45[view] [source] [discussion] 2026-01-22 01:30:57
>>vidarh+L33
I was more commenting on the language design here; the idea of indexing into a UTF-8 string and returning an ASCII character. What does the index count? Bytes? There doesn't seem to be a way to get UTF-8 characters from strings?

Ed: There seems to be an UTF-8 library:

https://github.com/jordanhubbard/nanolang/tree/main/modules/...

[go to top]