There are many, many array programmers who choose to write in a literate style. Popular code examples written for toy challenges often tend to be smart one liners whose algorithms cannot be easily put in multiple lines, so they may look unreadable for people unfamiliar with the languages. A terse compact code style often works well with the language's design.

If you'd like some examples of traditionally literate array programming, you can see:

- tangentstorm's J streams: https://www.twitch.tv/tangentstorm

- tangentstorm's J repositories: https://github.com/tangentstorm?tab=repositories&q=&type=&la...

- Dyalog's APL repositories: https://github.com/orgs/Dyalog/repositories?q=&type=&languag...

Not at all anathema. Many array programmers are very big on code documentation. J has joxygen to generate html docs from comments and JOD which is a code dictionary system.

https://analyzethedatanotthedrivel.org/the-jod-page/

https://code.jsoftware.com/wiki/Vocabulary/Libraries