I think the K team recognized these issues and tried to address them - at least partially - with Q and it's readable function names and SQL-like extensions. But

I think the K team recognized these issues and tried to address them - at least partially - with Q and it's readable function names and SQL-like extensions. But, AFAIK most Kdb programmers keep writing straight K instead. Don't know why either.