Part of those two days of commenting was that since K is interpreted all of the developers would hand-obfuscate all of the code so that the variables were a, b, c, etc. so that they would be slightly faster to parse than a multi-character string. This sort of thing is done all the time now, with JS to make it load faster, but his team at least didn't have any scripts to automatically turn developer-friendly code into interpreter-friendly code, they worked with the interpreter-friendly code version.
The notation-as-a-tool-of-thought camp prefers short identifiers on the principle that the more concise the expression, the easier it is to comprehend in total. This is not at all dissimilar from the general practices of mathematics.
mine was matlab. thinking of everything as an array, especially things that aren't arrays, was the first pattern I ever learned. I've never used APL in anger but for the most part it comes very easily to me. Maybe not the code golfing and/or idiomatic APL style that people like to post but, like, using the primitives to create increasingly elaborate arrays before discarding anything I don't want, that part has always felt very straight forward.
eg, instead of "echo yo >> file" you would "echo yo ≥ file"
Of course, supporting Unicode variable names doesn't mean a language supports Unicode anywhere, but it's a starting point for historical research at least.
That seems highly unlikely. Do you have a source, or are you sharing speculation as fact?
It’s more likely that APL symbols were included in Unicode as part of its mission to unify all the world’s scripts into single code set.
I used to think that Lisp was bad, with its "God coded the universe in Lisp", then I read only the first part of your sentence, and was "Woha, so APL predates thought?!"
In the Raku Programming Language there are several non-ASCII operators, although each of them has a pure ASCII equivalent. Some examples: ≤ vs <=, ≠ vs !=, ∈ vs (elem), etc.
The full list: https://docs.raku.org/language/unicode_ascii.html
- k has much fewer primitives. it's easier to remember a smaller set of operations.
- k is statically parsable. APL is not. we know the program structure simply by reading the code.
this is completely subjective. because you find APL more intuitive doesn't prove anything. to each their own.
And with regards to hotkeys, let's say you do Ctrl+alt+shift+esc+e to insert a unicode symbol, is that really better than just having a programming language where the common hotkeys are spelled out with a few ASCII characters?
Seems https://fluxkeyboard.com/ might be a great fit for programming in APL and similar.
Yeah, I’d love to discuss with colleagues how square-c works together with right double crowbar.
No, thanks.
x = √y
… would you pronounce it as “x, two parallel horizontal lines, V with a left hook, y”?
The symbols have a meaning that’s unrelated to their appearance. It’s the same in APL. The “square c” is just like “V with a left hook”.
“√” isn’t even a natural character, it’s a graphical delineator between an index and a radicand, similar to ÷ or % forms of division. By “obelus” (sharpened stick) do you mean dot above and below a line, a percent, a dagger or just a line?
Sure there will be enough confusion with ~10-30 extra symbols that aren’t even on a keyboard and may not have a single meaning or a name.
The point is, within the programming language, they do have a single meaning and a a name.