And not surprisingly that makes it less readable. It is a lot harder to have one-character names when you need to scroll across many pages to look up what they mean. So the more code you have, the longer code you need.…
I think a good introduction to this style of coding is the first "proof of concept" prototype interpreter for a small subset of J, also written by Whitney: https://code.jsoftware.com/wiki/Essays/Incunabulum Once I…
> Array languages are the most "obscure" of all paradigms I have looked into. Even concatenative ones have some few resources about how work. Have you tried looking at APL books? There are dozens of books on APL you can…
And not surprisingly that makes it less readable. It is a lot harder to have one-character names when you need to scroll across many pages to look up what they mean. So the more code you have, the longer code you need.…
I think a good introduction to this style of coding is the first "proof of concept" prototype interpreter for a small subset of J, also written by Whitney: https://code.jsoftware.com/wiki/Essays/Incunabulum Once I…
> Array languages are the most "obscure" of all paradigms I have looked into. Even concatenative ones have some few resources about how work. Have you tried looking at APL books? There are dozens of books on APL you can…