FWIW that's only the case for the website, in the local interpreter mode there appear to be specific functions for rendering a bunch of numbers as audio/images.
That surprised me too, but then I decided it was actually kinda brilliant. The alternative for when an array is "too big" to display is usually something like
[1 2 3 ... 99999]
Which is unsurprising, but not very usable. Audio is useful!
> The ^ above stands for the 3-dot cube dice glyph, which gets eaten by the HN backend, so it's ^ instead.
Just write "random" instead, then the snippet is copy-pasteable to the web-based interpreter. That's how you would normally write it out anyway, and interpreter will turn that into the dice glyph when run.
This is shows that you cannot make a language in the vacuum. There are other places and services that you need to integrate with and the use of these glyhps is making it harder.
I think using simple words: find, reverse, etc. is probably a better option.
Or it proves that HN's unicode stripping and intentional emoji blocking is making it harder than necessary to communicate some math and programming topics in their preferred notations.
(Also, this language supports the "simple words" approach but autoformats to the glyphs for final "readability".)
https://www.uiua.org/docs/&ap
https://www.uiua.org/docs/&imd