> it's hated by programmers who actually have to write code in it False. Many people really enjoy programming in it (myself included). > It doesn't tell you w

> it's hated by programmers who actually have to write code in it False. Many people really enjoy programming in it (myself included). > It doesn't tell you what caused an error or even where it happened. It just tells you something like "'rank" - and that's it. Since version 3.5 (~2 years ago?) it tells you exactly where the error occurred (prints out the line with a carat showing where in the line the error occurred). And with a little practice you easily learn what the common errors like 'rank & 'type mean. I actually find the error messages pretty helpful. > If you have a powerful 96-core machine, it's of no use to you because your K code will be using only a single core. Technically you can run q multi-threaded, but the typical architecture used in kdb+ systems will be using multiple processes, each doing one thing (data ingest, in-memory intraday data storage, data persistence, historical querying, gateway). For example it's generally fairly trivial to add a bunch of extra processes for historical queries so many users can query in parallel.