Hey there! Thanks for the kind thoughts. I love the ideas of K/Q/Erl/APL/J but the damn specifics, syntax, and wording is just so off-putting to most people. F

Hey there! Thanks for the kind thoughts. I love the ideas of K/Q/Erl/APL/J but the damn specifics, syntax, and wording is just so off-putting to most people. Frustrating because English is such a diverse language, but we insist on using our cryptic invented terms. Plus of course they write the documentation and tutorials as if you are solving a riddle.. I haven't started JS yet. I had to pick and choose my battles and writing all that in C alone was hard enough. I did build the first version of the "concept interpreter" using JS, so it would be pretty simple. I'd probably use fixed sized arrays and the rest of the asm.js stack if I did. People are looking for high performance. The key to the interpreter is simply converting each character of the source into an item in a list, then using open ended matching primitives to convert it into the proper parse tree, by detecting matching symbols, etc. The problem for real work w/ XXL+JS is the 1.7gb VM limit in V8, which no one seems to talk about. :) Come visit on #kq or #xxl on Freenode IRC when you have time.