4 ms·
People aren't really writing new systems in kdb+/q I feel like. And if you have a legacy kdb system why would you ever migrate to shatki? If you have to make t
by smabie 3y ago
People aren't really writing new systems in kdb+/q I feel like. And if you have a legacy kdb system why would you ever migrate to shatki?
If you have to make the choice between Shakti or some timeseries db + Python, Shakti would be a very suspicious choice. And I say this as someone who likes K and strongly dislikes Python.
- eismcc 3y agoJust gonna say, this is why i wrote KlongPy - an array language in Python that lets you interop with Python while also getting some array lang. efficiencies. Klong isn't as smooth as K, but it's still quite useful.
- 7thaccount 3y agoAre they not? What makes you think that? I honestly don't know myself, but am curious. Maybe they already found all the high paying customers and now there's nobody left that will pay that much? No idea.
- sudosysgen 3y agoPeople are, unfortunately, but because of inertia, and less and less. kdb/q are great for experimentation but for large scale systems it's a pain to maintain and it's often slower/scales worse than other solutions.