kdb VS hebigo

> And later array languages have mostly abandonned the crazy names in favour of actual words

Sharing this without comments:

https://github.com/KxSystems/kdb/blob/master/c/c/k.h

ah, I see you too are a disciple of the kdb school

Ah, after all these years, you've finally found it: a worthy opponent for kdb source code.

I am an experienced developer with 10+ years in various other languages (c++/python/ some scala). I am interested in getting into q/kdb+ after a recommendation from a friend in the industry. Does anyone out there have any suggestions on how to break into the industry Ive done the courses on https://code.kx.com/ and read a few suggested books but cant find any officially recognised certs I could get, and practical experience is limited ! Im not sure even id hire myself into such a role

For the curious, when I first ran into it it looked like this. That is not minified code, it's how people who write K write Java code. It was expected you would take that file and include it in your sources somewhere. The KDB protocol is actually very simple, basically writes out the types with a type tag, length and then the data in binary.

The Lissp transpiler incrementally compiles and executes each top-level form to Python. It needs to do this in case there's a macro definition that might affect the compilation of a subsequent form. If it's only executing definitions, this is harmless, but if you want to precompile the main module, it needs the guard, or the side effects will happen too.

If you want Python to be as customizable as Lissp, check out Hissp (and Hebigo).

Python's lambdas can have as many lines as you want. Just wrap parens around it. Hissp uses this form as a compilation target. Its REPL shows the Python compilation. Play around with it til you get it: https://github.com/gilch/hissp

The original Lisp's S-expression syntax was just supposed to be an intermediate language used by the compiler when processing the real language based on M-expressions, which kind of never took off. Numerous alternatives to S-expressions have been proposed, and some retain homoiconicity, another feature diagnostic of a Lisp (and one that ECMAScript lacks). For example, see Hebigo's readme, which shows a direct correspondence between its Python-like syntax and that of Hissp's default reader (Lissp), which uses the S-expressions. Julia can also be written in S-expressions, but this usually only used in macro definitions.

I think LoL is too CL-specific. If you know both languages first, you can pretty much translate, but since they'd be trying to learn Lisp in the first place, this is a bad idea.

On the other hand, [Hissp][1] has a pretty good tutorial for anyone coming from a Python background.

[1]: https://github.com/gilch/hissp

Hebigo: a whitespaceLisp isomorphic to Hissp that looks like Python.