First, this is an incredible achievement. I hope that the author(s) can monetize this project. I guess they can try to undercut kx.com's current insanely high subscription costs. Is that a goal? I ask because I cannot find the source code for the project, only downloadable compiled binaries. (No hate on that -- you are free to make lots of money from your hard work and apparent genius!)
Second, in my personal experience, most quants refer to the platform as "kdb+", which uses the languages q (directly), k (indirectly), and qSQL. Is there a reason why the website landing page does not mention kdb+? I assume this is intentional.
intentional. I consider kdb/kdb+ to be understood as the KX products - but L runs the same database style functionality (the qSQL is essentially just sugar atop the q/k code. Most of which is written in k [or C in L for a number of components])
Comments
First, this is an incredible achievement. I hope that the author(s) can monetize this project. I guess they can try to undercut kx.com's current insanely high subscription costs. Is that a goal? I ask because I cannot find the source code for the project, only downloadable compiled binaries. (No hate on that -- you are free to make lots of money from your hard work and apparent genius!)
Second, in my personal experience, most quants refer to the platform as "kdb+", which uses the languages q (directly), k (indirectly), and qSQL. Is there a reason why the website landing page does not mention kdb+? I assume this is intentional.
intentional. I consider kdb/kdb+ to be understood as the KX products - but L runs the same database style functionality (the qSQL is essentially just sugar atop the q/k code. Most of which is written in k [or C in L for a number of components])