4 ms·
This is a perfect illustration why normal people (like me, unlike Arthur) have problems working with his apparently brilliant creations, such as the k language.
by nine_k 12y ago
This is a perfect illustration why normal people (like me, unlike Arthur) have problems working with his apparently brilliant creations, such as the k language. The amount of information required to efficiently read (let alone write) such texts just does not fit into normal people's working memory. One-letter names and the absence of comments don't help either.
(WRT weird names: IIRC, some time ago kdb featured a number of functions named with digits, like '2' being the function to connect to a socket or something.)
- yang_guo 12y agoAs a guy with a terrible memory, I think of it the opposite way. For Q (and more so K), the actual number of distinct items to remember is very small, as basically anything complex is created by composition of the simple functions/variables. This way you don't need to remember nearly as many libraries/variables/function names, and also the function itself becomes its own description. That being said, for more production-heavy applications and interfacing with other languages, variable/function naming could be more descriptive :)
- icsa 12y agoAgreed. The small(ish) vocabulary of operators makes K easier for me to use. Would you rather write/read: DIVIDE X BY 5 GIVING Y or y=x/5; The first is COBOL (designed to make code easier for "normal" people to read. The second is C (which looks more like the math that we learn in grade school). k/APL/J simple moves further in the direction of math. As a far as descriptive names go, in k, names can always be aliased with longer names (assuming no conflicts). I do this when exposing a library k code as a web interface.