3 ms·
Wow, that was fascinating. K looks utterly mind-expanding, thanks for breaking this down. You obviously have some experience working with K, and it sounds like
by losvedir 12y ago
Wow, that was fascinating. K looks utterly mind-expanding, thanks for breaking this down.
You obviously have some experience working with K, and it sounds like at least Javascript, too? K is so foreign I expect it has a lot of interesting thoughts locked up in there that maybe don't get the attention they deserve.
Would you say there are any "killer features" of the language / environment that you miss when working with more traditional languages?
- icsa 12y agoKiller feature -------------- Not having to write: for(int i=0; i<n; i++) { ... } which generally obscures the fact that I'm trying to do a map or fold (e.g. - reduce) operation :).
- woah 12y agoES5
- deleted 12y ago[deleted]
- icsa 12y agoAnd now with less snark :). K/Q/kdb+ deploys a single executable and some additional k code (Q is written in k) in < 600KB uncompressed. Admin is very simple. Multicore use is trivial Hot code updates/upgrades (interpreter uses new definition on next execution) Code works the same (in most instances) for: * a single file/database * multiple files/tables * column files (for each table) * files on multiple machines (like MapReduce/Hadoop) with no changes.
- icsa 12y ago<pre> And now with less snark :). K/Q/kdb+ deploys a single executable and some additional k code (Q is written in k) in < 600KB uncompressed. Admin is very simple. Multicore use is trivial Hot code updates/upgrades (interpreter uses new definition on next execution) Code works the same (in most instances) for: * a single file/database * multiple files/tables * column files (for each table) * files on multiple machines (like MapReduce/Hadoop) with no changes. </pre>