Sure, kdb+ would probably be worth every penny even at $100k/year when it's the right tool for the job. I gather it's genuinely the best in-memory database for computing arrays of varying rank.
But a lot of the use cases these other tools are good for are small tasks every now and then. I feel kdb+ is in a different category.
where Q.fs is a function in a script thats bundled with the interpreter; the chunk size for reading the file into memory is adjustable by editing the function.
But a lot of the use cases these other tools are good for are small tasks every now and then. I feel kdb+ is in a different category.