K Language (2011)
I&#x27;m currently working on my own APL dialect. Like the author of K, I decided to not be bound to the restrictions of APL, and want it to be more functional. As I am also doing a lot of Lisp, a lot of ideas come from there as well.<p>The biggest difference in my language (which as of yet does not have a name) is that it is immutable, and function results are lazy. This means that it can be highly parallel, and the laziness means that there is much less synchronisation needed when parallelising computations.<p>I&#x27;m also making some of the syntax more traditional, in order to make large programs more manageable.<p>It&#x27;s implemented as a Kotlin multiplatform project, which means that I can build the interpreter for the JVM, native and Javascript.<p>Why am I talking about this? Well, it&#x27;s because my biggest issue with APL is that it&#x27;s not really suited for large programs (where large means on the order of 100 lines of code or more). Dyalog provides some extensions that make imperative programming easier, but the syntax is really ugly.<p>Thus, I&#x27;m trying to merge the idea of concise APL syntax together with typical functional programming. So you&#x27;ll be able to write code like this:<p><pre><code>    if (foo = bar) {
        a←⍉b
    } else {
        print &quot;debug message&quot;
        a←x∘.+y
    }
</code></pre>
Even though the core syntax is still APL, the structure of the program is much easier to understand, compared to the way you&#x27;d write it in APL.<p>I still don&#x27;t know if experiment will actually lead to something good, but at least it&#x27;s a fun project where I can play with Kotlin multiplatform support.<p>The code is on my Github, but I&#x27;m not linking it here since it&#x27;s quite early, and it&#x27;s not really usable yet (there are a lot of functions missing). I&#x27;m expecting anyone who actually looks it up anyway to understand that it&#x27;s not ready yet.