What does 'tacit' mean in the context of "A tacit array programming language"? What is being implied?

I'd also like someone to point me to a more beginner friendly primer on the benefits of an array based programming language. I can think of a few areas like bitmaps/graphics and audio. But what about more general purpose logic? This looks good for handling chunks of data but what about boring logic, e.g. GUI programs? Edit: to be clear: what problems do array programming languages solve effectively?

> Combining these already terse systems results in code with a very high information density and little syntactic noise.

I like the idea of glyphs but it does not seem to mix well with the above use of the word tacit as these symbols imply nothing until you learn their meaning. IMO replacing the symbols with words feels more implied as one could easily read the code without needing a mental map of symbols. Kinda how Ada programs read as a contract of what it will explicitly do.

However, there is a good argument to be made for glyphs: they eliminate the human language barrier making them more applicable and perhaps adaptable to non-English speaking programmers.

I also wonder if you can use glyph based languages as a human language agnostic syntax. You could map language to the symbols using implicit words per symbol and instantly translate code between languages. This way a Japanese programmer can see the meaning of the symbol in their native language IDE, save it, then a Farsi speaking programmer could open it and see the symbols in Farsi. Comments would be a challenge but translation of some form can be used.