kdb
ok
Our great sponsors
| kdb | ok | |
|---|---|---|
| 3 | 30 | |
| 41 | 575 | |
| - | - | |
| 5.6 | 4.2 | |
| 3 months ago | 6 months ago | |
| q | JavaScript | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kdb
- Q Coding Guidelines by Finos
-
Ngn/k (free K implementation)
> let's say I have a finance team that have never heard of it - why might they be interested?
In my experience it's very good at quickly developing real-time analytics applications with only a small set of developers. A couple of q developers can develop, maintain and operate the server side of 5 or 6 separate applications without breaking a sweat. Changes come in at a high speed too.
It's a highly interactive language. A bit like a lisp, you start up a q process, open a port and then you iterate and update your application live without needing to restart. Typically on our projects we've had a well iterated program running in QA for a day or 2 before opening a PR (which becomes more of a formality for getting the solution to the problem into prod at that stage).
The q language itself is quite wordy. Check the reference page: https://code.kx.com/q/ref/ Many programs written in q consist mainly of the key words with the special operators interspersed. Also see some example libraries: https://github.com/finos/kdb
It's been a fairly stable language to work with, having few breaking changes between successive versions. q code written 8/9/10 years ago on older versions will most likely still run the same today. We have source code on one project at work which hasn't had a code change in 6 years now (despite moving through different versions 2.8->3.0->3.3->3.5->4.0) and it runs daily without a hiccup.
Mostly it's a joy working with it because I feel like I get to tell the computer what I want it to do, without also having to tell it how to do it.
ok
- Trees
- Programming in K
- k on pdp11
-
Origins of J
This - https://github.com/JohnEarnest/ok - can also be used sometimes...
- Trees in K
-
Coding in the Shadows: Hidden Gems of Lisp, Clojure, and friends
If you want to try out K, there are some open source implementations, like John Earnest's oK which has a REPL and a calculator-like interface for mobile phones with a charting feature.
-
Why Lisp Syntax Works
and have the programmer use the word "barchart", they instead prefer to use the definition itself. The word "barchart" has a specific meaning (here, an ascii "bar chart" of 0s and 1s, showing the relative sizes of the values of input array x), but "{x>\:!|/x}" might be useful for more than just bar charts. This idiom contains smaller idioms like "count til max" (!|/) which in turn contains "max" (|/).
Being able to see the code makes it easier to explore and tweak to your specific needs. But more importantly, there are no "official" names for concepts like "count til max". That's just my personal name for it. A python programmer would call it "range". You could come up with your own name for (!|/) that makes perfect sense to you. But that name will probably be longer than its definition, and less flexible.
[1] https://github.com/JohnEarnest/ok/blob/gh-pages/examples/idi...
-
Animated unknown pleasures in 3 lines of K
check out oK[0] by John Earnest, who is the author of the content of this post
it is well-written manual and is a great jumping off point
there is a k-enthusiast element.io server[1] where you can ask any question you like. folks are friendly!
[0] https://github.com/JohnEarnest/ok
[1] https://matrix.to/#/#aplfarm-k:matrix.org
- APLcart – Find your way in APL