5 ms·

This kind of story is what I enjoy so much about HN. I wish Kdb+ or Shakti had dramatically lower costs for those industries that don't have access to banking c

This kind of story is what I enjoy so much about HN. I wish Kdb+ or Shakti had dramatically lower costs for those industries that don't have access to banking cash. I know open source versions exist, but I understand them to mostly be toys and not really production worthy.

deleted 3y ago
[deleted]
DrDroop 3y ago
K is at the end of the day a fancy calculator, I think for most workloads you can use the open source version called ngn/k
- avmich 3y ago
  This - https://github.com/JohnEarnest/ok https://github.com/JohnEarnest/ok - can also be used sometimes...
- anotherjhacker 3y ago
  Sure, a fancy calculator that supports rather efficient execution on ridiculously large machine farms. What some people might call the implementation language for a database engine.
- kelas 3y ago
  > k is a fancy calculator [put your favorite Java here] is also a fancy calculator by the virtue of Turing completeness. what’s your point?
- 7thaccount 3y ago
  Quant firms don't spend millions on what is just "a fancy calculator". It's more than that. It's a high performance combination of programming language and database that are tightly integrated together and more than the sum of their parts. I wouldn't want to write generic software in it, but it's pretty powerful for analysis.
eismcc 3y ago
KlongPy sits on NumPy so gets pretty far. For some features, it’s still early days. Http://klongpy.org
RyanHamilton 3y ago
As the author of an open source version (https://www.timestored.com/jq/ https://www.timestored.com/jq/) I wish the same but I fear the time has passed. Two factors: 1. The other technologies are evolving to take parts of kdb+ that made it special quicker than kdb+ is evolving. See arrow / parquet / numpy / kafka, they each solve parts but kdb+ had them all 10 years ago in <2MB. 2. The ratio of learners to advanced programmers has increased every year for the last 20 years. The languages that have gained popularity in that time range are those with the easiest learning curve. Most beginners no longer want to sit with a book frustrated on 2 characters for half a day.
- tangentstorm 3y ago
  Oh, interesting! I heard other array programmers talking about jq, and (having not seen your website) went off to study the json transformation language, which is also kind of cool, but nothing to do with kdb or q. :)
- bigbillheck 3y ago
  > Most beginners no longer want Most beginners never wanted that.
  - kelas 3y ago
    guys, my two pennies: most beginners have no idea what they want. but what we know is that what they don’t want is to produce more endless ugly and buggy code into the world - we’ve produced enough of that before they learned how to locate their asse(t)s.
  - RyanHamilton 3y ago
    You are correct. I guess it's more accurate to say, most beginners are no longer forced to learn step by step from a book. Now they ask google/SO/chatGPT and use that if it works with a few tweaks. Kdb+ has very few core concepts, most of which since they are symbols are hard to google.

deleted 3y ago

[deleted]

DrDroop 3y ago

K is at the end of the day a fancy calculator, I think for most workloads you can use the open source version called ngn/k

avmich 3y ago
This - https://github.com/JohnEarnest/ok https://github.com/JohnEarnest/ok - can also be used sometimes...
anotherjhacker 3y ago
Sure, a fancy calculator that supports rather efficient execution on ridiculously large machine farms. What some people might call the implementation language for a database engine.
kelas 3y ago
> k is a fancy calculator [put your favorite Java here] is also a fancy calculator by the virtue of Turing completeness. what’s your point?
7thaccount 3y ago
Quant firms don't spend millions on what is just "a fancy calculator". It's more than that. It's a high performance combination of programming language and database that are tightly integrated together and more than the sum of their parts. I wouldn't want to write generic software in it, but it's pretty powerful for analysis.

eismcc 3y ago

KlongPy sits on NumPy so gets pretty far. For some features, it’s still early days. Http://klongpy.org

RyanHamilton 3y ago

As the author of an open source version (https://www.timestored.com/jq/ https://www.timestored.com/jq/) I wish the same but I fear the time has passed. Two factors: 1. The other technologies are evolving to take parts of kdb+ that made it special quicker than kdb+ is evolving. See arrow / parquet / numpy / kafka, they each solve parts but kdb+ had them all 10 years ago in <2MB. 2. The ratio of learners to advanced programmers has increased every year for the last 20 years. The languages that have gained popularity in that time range are those with the easiest learning curve. Most beginners no longer want to sit with a book frustrated on 2 characters for half a day.

tangentstorm 3y ago
Oh, interesting! I heard other array programmers talking about jq, and (having not seen your website) went off to study the json transformation language, which is also kind of cool, but nothing to do with kdb or q. :)
bigbillheck 3y ago
> Most beginners no longer want Most beginners never wanted that.
- kelas 3y ago
  guys, my two pennies: most beginners have no idea what they want. but what we know is that what they don’t want is to produce more endless ugly and buggy code into the world - we’ve produced enough of that before they learned how to locate their asse(t)s.
- RyanHamilton 3y ago
  You are correct. I guess it's more accurate to say, most beginners are no longer forced to learn step by step from a book. Now they ask google/SO/chatGPT and use that if it works with a few tweaks. Kdb+ has very few core concepts, most of which since they are symbols are hard to google.