Now, I don't know either K or Q, but I have a very, very, very hard time believing that they are too terse and unreadable because of that.
From my experience, the "improvements in readability" are of course good, but they only shorten the time to master the language. Once you learn the language well enough, it becomes readable. And the very few syntactic issues which are objectively hard to distinguish/are confusing the eye, etc. tend to be worked around with formatting and font settings.
Written Japanese is totally impossible to read if you don't know it - and it takes reasonably longer to learn it. However, once you know it, it's readable. A Japanese person reading a newspaper in Japanese uses as much effort as me reading a newspaper in my native language.
[1] From Pascal and later Delphi users.
[2] From C users.
[3] From PERL users.
[4] From PHP users.
[5] From Python users.I have not found this definition of "read" to be common in other language communities.
Maybe you're one of the happy few that spends more time writing code than reading it, but for an overwhelming majority of devs, the opposite is true. That's why even small readability improvements matter much more than a couple cool tricks a language may have.