2 ms·
The k family likes to be the whole stack; they would view libc as an unnecessary huge[0] dependency. [0] To k, every other language/library/program is too big.
by yjftsjthsd-h 7y ago
The k family likes to be the whole stack; they would view libc as an unnecessary huge[0] dependency.
[0] To k, every other language/library/program is too big.
- smabie 7y agoSeeing that libc is undoubtedly already loaded in memory as a dynamic lib on all systems, that doesn't make much sense. Moreover kdb+/q links to libc, and it has very good performance and memory usage.